Date   

HBLINK

fred sant
 

File "./web_tables.py", line 48, in <module>
    from jinja2 import Environment, PackageLoader, select_autoescape
ImportError: cannot import name select_autoescape


NEED HELP WITH THIS ERROR. THIS IS FOR HBLINK DASHBOAR.


Re: Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

Steve N4IRS
 

I do believe that 3119 is Iowa Statewide I don't know that bridging it to P25 is a good idea. That is outside of the scope of DVSwitch bridging but I think you may want to reconsider using that TG.
 

On 3/13/19 7:52 PM, Ray Harden wrote:

I am happy to rerun the test, yes, I see that I failed to key the P25 radio after key of the DMR.

 

Just for curiosity I decided to run the ./bridge.sh process.  To my inexperienced eye the activity (log attached) during the last four minutes of the run certainly looks impressive.  So what happened to the audio?  Various statements indicate “PTT ON”,  “P25 TX state -= ON”, but not a sound from either the Motorola Astro Spectra or the TYT MD-380 logged to Brandmeister at a nearby DMR repeater.

 

M: 2019-03-13 22:42:29.131 MMDVM_Bridge-20180423 is running

M: 2019-03-13 22:42:39.234 DMR, Logged into the master successfully

M: 2019-03-13 22:42:51.268 Adding W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.274 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.631 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:42:57.935 Received end of transmission

M: 2019-03-13 22:43:12.362 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:12.363 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:12.364 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:12.893 PTT on

M: 2019-03-13 22:43:12.894 P25, TX state = ON

I: 2019-03-13 22:43:12.894 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:13.060 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:43:13.778 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:43:14.498 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W0RAY DMR ID: 311924'

M: 2019-03-13 22:43:15.216 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W0RAY DMR ID: 3119240'

M: 2019-03-13 22:43:15.698 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 1% packet loss, BER: 0.0%

M: 2019-03-13 22:43:15.699 PTT off (keyed for 2806 ms)

M: 2019-03-13 22:43:15.704 P25, TX state = OFF

M: 2019-03-13 22:43:44.719 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:44.720 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:44.720 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:45.221 PTT on

M: 2019-03-13 22:43:45.235 P25, TX state = ON

I: 2019-03-13 22:43:45.235 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:46.161 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:46.881 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:47.008 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 5% packet loss, BER: 0.0%

M: 2019-03-13 22:43:47.009 PTT off (keyed for 1788 ms)

M: 2019-03-13 22:43:47.014 P25, TX state = OFF

M: 2019-03-13 22:44:00.628 Currently linked repeaters:

M: 2019-03-13 22:44:00.628     W0RAY      (192.168.3.130:42010) 4/120

W: 2019-03-13 22:44:04.998 No response from 31900, unlinking

M: 2019-03-13 22:44:18.316 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:44:18.317 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:44:18.318 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:44:18.819 PTT on

M: 2019-03-13 22:44:18.824 P25, TX state = ON

I: 2019-03-13 22:44:18.824 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:44:18.884 Linked to reflector 31900 by W0RAY

M: 2019-03-13 22:44:18.923 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:44:19.646 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:44:20.123 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 0% packet loss, BER: 0.0%

M: 2019-03-13 22:44:20.123 PTT off (keyed for 1304 ms)

M: 2019-03-13 22:44:20.128 P25, TX state = OFF

M: 2019-03-13 22:45:01.536 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:45:01.546 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:45:05.518 Received end of transmission

M: 2019-03-13 22:45:29.085 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:45:29.086 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:45:29.086 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:45:29.587 PTT on

M: 2019-03-13 22:45:29.595 P25, TX state = ON

I: 2019-03-13 22:45:29.595 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:45:30.983 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 9% packet loss, BER: 0.0%

M: 2019-03-13 22:45:30.984 PTT off (keyed for 1397 ms)

M: 2019-03-13 22:45:30.989 P25, TX state = OFF

M: 2019-03-13 22:46:00.740 Currently linked repeaters:

M: 2019-03-13 22:46:00.740     W0RAY      (192.168.3.130:42010) 4/120

^C

 

Your synopsis focused mainly on the TalkGroups, 3119 – Brandmeister and 31900 – assigned by me within the P25Repeater and Astro Spectra radios.  I am not clear about what to do with any of this.

 

Are you highlighting these for changes and if so what should I use?  My reading and research of the various fields led me to the values you see.  Too many unclear references to TG, not differentiating between whether to use a Brandmeister TG or a P25 TG.

 

The audio values for agcGain are both -15 in the two A_B.ini parameters.

 

Thank you very much for your valuable time.

 

RayH   w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 11:06 AM
To: main@DVSwitch.groups.io.
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I do not see a transmission from P25, so I'll address DMR -> P25

We see the TX in the MB log here:
M: 2019-03-13 14:27:10.248 DMR Slot 2, received network voice header from W0RAY to TG 3119

In AB_DMR we see this:
I: 2019-03-13 14:27:10.249 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

In AB_P25 we see this:
I: 2019-03-13 14:27:10.250 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240
M: 2019-03-13 14:27:10.806 PTT on

Back to the MB log we see this:
I: 2019-03-13 14:27:10.808 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

And finally in the P25Reflector log we see:
M: 2019-03-13 14:27:24.942 Transmission from W0RAY at W0RAY      to TG 31900

31900?
Where is that coming from? In AB_P25 we see this:
M: 2019-03-13 14:26:50.193 Setting [AMBE_AUDIO] txTg -> 31900

OK, so that explains the final output TG.

Now, I'm looking at the audio level settings.
In AB_DMR I see this:
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_DMR.ini?

In AB_P25 I see this:
M: 2019-03-13 14:26:50.194 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:50.194 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_P25.ini?

Steve N4IRS


On 3/13/2019 11:44 AM, Ray Harden wrote:

The attached file is the correct one with the same name.  Unfortunately I mistakenly included a file from an earlier run in the former .ZIP.   

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 10:06 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I don't think the AB logLevel is set at 2.  I don't see a single transmission from P25. If the AB logs do not look like this don't send the files until they do.

I: 2019-03-13 14:26:44.924 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-03-13 14:26:44.924 Created by Mike N4IRR and Steve N4IRS
I: 2019-03-13 14:26:44.924 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 This software is for use on amateur radio networks only,
I: 2019-03-13 14:26:44.924 it is to be used for educational purposes only. Its use on
I: 2019-03-13 14:26:44.924 commercial networks is strictly prohibited.
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 Analog Bridge is starting
M: 2019-03-13 14:26:44.926 Setting [GENERAL] logLevel -> 2
M: 2019-03-13 14:26:44.926 Setting [GENERAL] exportMetadata -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-03-13 14:26:44.926 Setting [GENERAL] decoderFallBack -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] useEmulator -> true
M: 2019-03-13 14:26:44.927 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-03-13 14:26:44.927 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useMicrophone -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useVox -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxDecay -> 2
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxTrigger -> 200
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] server -> 127.0.0.1
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] fromDMRPort -> 31100
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] toDMRPort -> 31103
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] gatewayDmrId -> 311924009
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] repeaterID -> 3119240
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTg -> 31900
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-03-13 14:26:44.928 Setting [USRP] server -> 127.0.0.1
M: 2019-03-13 14:26:44.928 Setting [USRP] toASLPort -> 32001
M: 2019-03-13 14:26:44.928 Setting [USRP] fromASLPort -> 34001
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrGain -> 0.35
M: 2019-03-13 14:26:44.929 Setting [DV3000] server -> 127.0.0.1
M: 2019-03-13 14:26:44.929 Setting [DV3000] port -> 2460
W: 2019-03-13 14:26:44.929 ioctl reset error
W: 2019-03-13 14:26:44.929 ioctl speed error
W: 2019-03-13 14:26:44.929 ioctl stereo error
W: 2019-03-13 14:26:44.929 ioctl setfmt error
M: 2019-03-13 14:26:44.929 Audio In/Out Device: /dev/null
I: 2019-03-13 14:26:44.929 Open UDP listener on 127.0.0.1:31100
I: 2019-03-13 14:26:44.930 Open USRP on 127.0.0.1:32001
M: 2019-03-13 14:26:44.930 Connecting to DV3000 hardware......
W: 2019-03-13 14:26:45.947 DV3000 not found at 127.0.0.1:2460
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2019-03-13 14:26:46.747 Subscriber IDs loaded: 125115
I: 2019-03-13 14:26:46.747 Default extended metadata <311924009>
I: 2019-03-13 14:26:46.748 Connecting to emulator on host 127.0.0.1:2470
W: 2019-03-13 14:26:46.748 Using software MBE decoder version 1.2.3
W: 2019-03-13 14:26:46.748 Using software OP25 IMBE/AMBE vocoder
I: 2019-03-13 14:26:46.749 Starting Analog_Bridge --> USRP thread
I: 2019-03-13 14:26:46.749 Open UDP listener on 127.0.0.1:34001
I: 2019-03-13 14:26:46.749 Starting USRP --> HB_Bridge thread

On 3/13/2019 10:51 AM, Ray Harden wrote:

A_B logs now have logLevel = 2

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 9:10 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

The AB logs do not contain the settings. Make sure you have
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

Set logLevel to 2 or below and capture all again.

On 3/13/2019 8:58 AM, Ray Harden wrote:

Responding to your request … 5 logs run without the  [  &  ], All Debugs @ 0 this time; keyed TYT-380 DMR radio on Brandmeister TG 3119 first, then a few seconds later the P25 – TG31900 mobile radio >> P25 repeater and its MMDVM-P25-Enabled TG31900 software.  There is a really impressive amount of setup to do this – I have probably missed something!

 

v/r

 

RayH    w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, March 12, 2019 6:20 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

 



Re: Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

Steve N4IRS
 

I was highlighting the traffic as it passed through the bridge. I did notice the change from 3119 to 311900. I saw where it was generated.
Change the 2 audio levels I highlighted to 1 (unity) and see if you have audio.

On 3/13/19 7:52 PM, Ray Harden wrote:

I am happy to rerun the test, yes, I see that I failed to key the P25 radio after key of the DMR.

 

Just for curiosity I decided to run the ./bridge.sh process.  To my inexperienced eye the activity (log attached) during the last four minutes of the run certainly looks impressive.  So what happened to the audio?  Various statements indicate “PTT ON”,  “P25 TX state -= ON”, but not a sound from either the Motorola Astro Spectra or the TYT MD-380 logged to Brandmeister at a nearby DMR repeater.

 

M: 2019-03-13 22:42:29.131 MMDVM_Bridge-20180423 is running

M: 2019-03-13 22:42:39.234 DMR, Logged into the master successfully

M: 2019-03-13 22:42:51.268 Adding W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.274 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.631 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:42:57.935 Received end of transmission

M: 2019-03-13 22:43:12.362 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:12.363 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:12.364 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:12.893 PTT on

M: 2019-03-13 22:43:12.894 P25, TX state = ON

I: 2019-03-13 22:43:12.894 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:13.060 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:43:13.778 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:43:14.498 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W0RAY DMR ID: 311924'

M: 2019-03-13 22:43:15.216 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W0RAY DMR ID: 3119240'

M: 2019-03-13 22:43:15.698 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 1% packet loss, BER: 0.0%

M: 2019-03-13 22:43:15.699 PTT off (keyed for 2806 ms)

M: 2019-03-13 22:43:15.704 P25, TX state = OFF

M: 2019-03-13 22:43:44.719 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:44.720 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:44.720 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:45.221 PTT on

M: 2019-03-13 22:43:45.235 P25, TX state = ON

I: 2019-03-13 22:43:45.235 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:46.161 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:46.881 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:47.008 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 5% packet loss, BER: 0.0%

M: 2019-03-13 22:43:47.009 PTT off (keyed for 1788 ms)

M: 2019-03-13 22:43:47.014 P25, TX state = OFF

M: 2019-03-13 22:44:00.628 Currently linked repeaters:

M: 2019-03-13 22:44:00.628     W0RAY      (192.168.3.130:42010) 4/120

W: 2019-03-13 22:44:04.998 No response from 31900, unlinking

M: 2019-03-13 22:44:18.316 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:44:18.317 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:44:18.318 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:44:18.819 PTT on

M: 2019-03-13 22:44:18.824 P25, TX state = ON

I: 2019-03-13 22:44:18.824 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:44:18.884 Linked to reflector 31900 by W0RAY

M: 2019-03-13 22:44:18.923 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:44:19.646 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:44:20.123 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 0% packet loss, BER: 0.0%

M: 2019-03-13 22:44:20.123 PTT off (keyed for 1304 ms)

M: 2019-03-13 22:44:20.128 P25, TX state = OFF

M: 2019-03-13 22:45:01.536 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:45:01.546 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:45:05.518 Received end of transmission

M: 2019-03-13 22:45:29.085 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:45:29.086 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:45:29.086 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:45:29.587 PTT on

M: 2019-03-13 22:45:29.595 P25, TX state = ON

I: 2019-03-13 22:45:29.595 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:45:30.983 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 9% packet loss, BER: 0.0%

M: 2019-03-13 22:45:30.984 PTT off (keyed for 1397 ms)

M: 2019-03-13 22:45:30.989 P25, TX state = OFF

M: 2019-03-13 22:46:00.740 Currently linked repeaters:

M: 2019-03-13 22:46:00.740     W0RAY      (192.168.3.130:42010) 4/120

^C

 

Your synopsis focused mainly on the TalkGroups, 3119 – Brandmeister and 31900 – assigned by me within the P25Repeater and Astro Spectra radios.  I am not clear about what to do with any of this.

 

Are you highlighting these for changes and if so what should I use?  My reading and research of the various fields led me to the values you see.  Too many unclear references to TG, not differentiating between whether to use a Brandmeister TG or a P25 TG.

 

The audio values for agcGain are both -15 in the two A_B.ini parameters.

 

Thank you very much for your valuable time.

 

RayH   w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 11:06 AM
To: main@DVSwitch.groups.io.
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I do not see a transmission from P25, so I'll address DMR -> P25

We see the TX in the MB log here:
M: 2019-03-13 14:27:10.248 DMR Slot 2, received network voice header from W0RAY to TG 3119

In AB_DMR we see this:
I: 2019-03-13 14:27:10.249 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

In AB_P25 we see this:
I: 2019-03-13 14:27:10.250 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240
M: 2019-03-13 14:27:10.806 PTT on

Back to the MB log we see this:
I: 2019-03-13 14:27:10.808 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

And finally in the P25Reflector log we see:
M: 2019-03-13 14:27:24.942 Transmission from W0RAY at W0RAY      to TG 31900

31900?
Where is that coming from? In AB_P25 we see this:
M: 2019-03-13 14:26:50.193 Setting [AMBE_AUDIO] txTg -> 31900

OK, so that explains the final output TG.

Now, I'm looking at the audio level settings.
In AB_DMR I see this:
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_DMR.ini?

In AB_P25 I see this:
M: 2019-03-13 14:26:50.194 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:50.194 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_P25.ini?

Steve N4IRS


On 3/13/2019 11:44 AM, Ray Harden wrote:

The attached file is the correct one with the same name.  Unfortunately I mistakenly included a file from an earlier run in the former .ZIP.   

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 10:06 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I don't think the AB logLevel is set at 2.  I don't see a single transmission from P25. If the AB logs do not look like this don't send the files until they do.

I: 2019-03-13 14:26:44.924 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-03-13 14:26:44.924 Created by Mike N4IRR and Steve N4IRS
I: 2019-03-13 14:26:44.924 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 This software is for use on amateur radio networks only,
I: 2019-03-13 14:26:44.924 it is to be used for educational purposes only. Its use on
I: 2019-03-13 14:26:44.924 commercial networks is strictly prohibited.
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 Analog Bridge is starting
M: 2019-03-13 14:26:44.926 Setting [GENERAL] logLevel -> 2
M: 2019-03-13 14:26:44.926 Setting [GENERAL] exportMetadata -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-03-13 14:26:44.926 Setting [GENERAL] decoderFallBack -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] useEmulator -> true
M: 2019-03-13 14:26:44.927 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-03-13 14:26:44.927 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useMicrophone -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useVox -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxDecay -> 2
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxTrigger -> 200
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] server -> 127.0.0.1
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] fromDMRPort -> 31100
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] toDMRPort -> 31103
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] gatewayDmrId -> 311924009
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] repeaterID -> 3119240
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTg -> 31900
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-03-13 14:26:44.928 Setting [USRP] server -> 127.0.0.1
M: 2019-03-13 14:26:44.928 Setting [USRP] toASLPort -> 32001
M: 2019-03-13 14:26:44.928 Setting [USRP] fromASLPort -> 34001
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrGain -> 0.35
M: 2019-03-13 14:26:44.929 Setting [DV3000] server -> 127.0.0.1
M: 2019-03-13 14:26:44.929 Setting [DV3000] port -> 2460
W: 2019-03-13 14:26:44.929 ioctl reset error
W: 2019-03-13 14:26:44.929 ioctl speed error
W: 2019-03-13 14:26:44.929 ioctl stereo error
W: 2019-03-13 14:26:44.929 ioctl setfmt error
M: 2019-03-13 14:26:44.929 Audio In/Out Device: /dev/null
I: 2019-03-13 14:26:44.929 Open UDP listener on 127.0.0.1:31100
I: 2019-03-13 14:26:44.930 Open USRP on 127.0.0.1:32001
M: 2019-03-13 14:26:44.930 Connecting to DV3000 hardware......
W: 2019-03-13 14:26:45.947 DV3000 not found at 127.0.0.1:2460
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2019-03-13 14:26:46.747 Subscriber IDs loaded: 125115
I: 2019-03-13 14:26:46.747 Default extended metadata <311924009>
I: 2019-03-13 14:26:46.748 Connecting to emulator on host 127.0.0.1:2470
W: 2019-03-13 14:26:46.748 Using software MBE decoder version 1.2.3
W: 2019-03-13 14:26:46.748 Using software OP25 IMBE/AMBE vocoder
I: 2019-03-13 14:26:46.749 Starting Analog_Bridge --> USRP thread
I: 2019-03-13 14:26:46.749 Open UDP listener on 127.0.0.1:34001
I: 2019-03-13 14:26:46.749 Starting USRP --> HB_Bridge thread

On 3/13/2019 10:51 AM, Ray Harden wrote:

A_B logs now have logLevel = 2

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 9:10 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

The AB logs do not contain the settings. Make sure you have
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

Set logLevel to 2 or below and capture all again.

On 3/13/2019 8:58 AM, Ray Harden wrote:

Responding to your request … 5 logs run without the  [  &  ], All Debugs @ 0 this time; keyed TYT-380 DMR radio on Brandmeister TG 3119 first, then a few seconds later the P25 – TG31900 mobile radio >> P25 repeater and its MMDVM-P25-Enabled TG31900 software.  There is a really impressive amount of setup to do this – I have probably missed something!

 

v/r

 

RayH    w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, March 12, 2019 6:20 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

 



Re: Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

Steve N4IRS
 

I do not see a transmission from P25, so I'll address DMR -> P25

We see the TX in the MB log here:
M: 2019-03-13 14:27:10.248 DMR Slot 2, received network voice header from W0RAY to TG 3119

In AB_DMR we see this:
I: 2019-03-13 14:27:10.249 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

In AB_P25 we see this:
I: 2019-03-13 14:27:10.250 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240
M: 2019-03-13 14:27:10.806 PTT on

Back to the MB log we see this:
I: 2019-03-13 14:27:10.808 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

And finally in the P25Reflector log we see:
M: 2019-03-13 14:27:24.942 Transmission from W0RAY at W0RAY      to TG 31900

31900?
Where is that coming from? In AB_P25 we see this:
M: 2019-03-13 14:26:50.193 Setting [AMBE_AUDIO] txTg -> 31900

OK, so that explains the final output TG.

Now, I'm looking at the audio level settings.
In AB_DMR I see this:
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_DMR.ini?

In AB_P25 I see this:
M: 2019-03-13 14:26:50.194 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:50.194 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_P25.ini?

Steve N4IRS




On 3/13/2019 11:44 AM, Ray Harden wrote:

The attached file is the correct one with the same name.  Unfortunately I mistakenly included a file from an earlier run in the former .ZIP.   

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 10:06 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I don't think the AB logLevel is set at 2.  I don't see a single transmission from P25. If the AB logs do not look like this don't send the files until they do.

I: 2019-03-13 14:26:44.924 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-03-13 14:26:44.924 Created by Mike N4IRR and Steve N4IRS
I: 2019-03-13 14:26:44.924 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 This software is for use on amateur radio networks only,
I: 2019-03-13 14:26:44.924 it is to be used for educational purposes only. Its use on
I: 2019-03-13 14:26:44.924 commercial networks is strictly prohibited.
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 Analog Bridge is starting
M: 2019-03-13 14:26:44.926 Setting [GENERAL] logLevel -> 2
M: 2019-03-13 14:26:44.926 Setting [GENERAL] exportMetadata -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-03-13 14:26:44.926 Setting [GENERAL] decoderFallBack -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] useEmulator -> true
M: 2019-03-13 14:26:44.927 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-03-13 14:26:44.927 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useMicrophone -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useVox -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxDecay -> 2
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxTrigger -> 200
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] server -> 127.0.0.1
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] fromDMRPort -> 31100
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] toDMRPort -> 31103
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] gatewayDmrId -> 311924009
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] repeaterID -> 3119240
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTg -> 31900
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-03-13 14:26:44.928 Setting [USRP] server -> 127.0.0.1
M: 2019-03-13 14:26:44.928 Setting [USRP] toASLPort -> 32001
M: 2019-03-13 14:26:44.928 Setting [USRP] fromASLPort -> 34001
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrGain -> 0.35
M: 2019-03-13 14:26:44.929 Setting [DV3000] server -> 127.0.0.1
M: 2019-03-13 14:26:44.929 Setting [DV3000] port -> 2460
W: 2019-03-13 14:26:44.929 ioctl reset error
W: 2019-03-13 14:26:44.929 ioctl speed error
W: 2019-03-13 14:26:44.929 ioctl stereo error
W: 2019-03-13 14:26:44.929 ioctl setfmt error
M: 2019-03-13 14:26:44.929 Audio In/Out Device: /dev/null
I: 2019-03-13 14:26:44.929 Open UDP listener on 127.0.0.1:31100
I: 2019-03-13 14:26:44.930 Open USRP on 127.0.0.1:32001
M: 2019-03-13 14:26:44.930 Connecting to DV3000 hardware......
W: 2019-03-13 14:26:45.947 DV3000 not found at 127.0.0.1:2460
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2019-03-13 14:26:46.747 Subscriber IDs loaded: 125115
I: 2019-03-13 14:26:46.747 Default extended metadata <311924009>
I: 2019-03-13 14:26:46.748 Connecting to emulator on host 127.0.0.1:2470
W: 2019-03-13 14:26:46.748 Using software MBE decoder version 1.2.3
W: 2019-03-13 14:26:46.748 Using software OP25 IMBE/AMBE vocoder
I: 2019-03-13 14:26:46.749 Starting Analog_Bridge --> USRP thread
I: 2019-03-13 14:26:46.749 Open UDP listener on 127.0.0.1:34001
I: 2019-03-13 14:26:46.749 Starting USRP --> HB_Bridge thread

On 3/13/2019 10:51 AM, Ray Harden wrote:

A_B logs now have logLevel = 2

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 9:10 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

The AB logs do not contain the settings. Make sure you have
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

Set logLevel to 2 or below and capture all again.

On 3/13/2019 8:58 AM, Ray Harden wrote:

Responding to your request … 5 logs run without the  [  &  ], All Debugs @ 0 this time; keyed TYT-380 DMR radio on Brandmeister TG 3119 first, then a few seconds later the P25 – TG31900 mobile radio >> P25 repeater and its MMDVM-P25-Enabled TG31900 software.  There is a really impressive amount of setup to do this – I have probably missed something!

 

v/r

 

RayH    w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, March 12, 2019 6:20 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 



Re: Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

Ray Harden
 

I am happy to rerun the test, yes, I see that I failed to key the P25 radio after key of the DMR.

 

Just for curiosity I decided to run the ./bridge.sh process.  To my inexperienced eye the activity (log attached) during the last four minutes of the run certainly looks impressive.  So what happened to the audio?  Various statements indicate “PTT ON”,  “P25 TX state -= ON”, but not a sound from either the Motorola Astro Spectra or the TYT MD-380 logged to Brandmeister at a nearby DMR repeater.

 

M: 2019-03-13 22:42:29.131 MMDVM_Bridge-20180423 is running

M: 2019-03-13 22:42:39.234 DMR, Logged into the master successfully

M: 2019-03-13 22:42:51.268 Adding W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.274 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:42:51.631 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:42:57.935 Received end of transmission

M: 2019-03-13 22:43:12.362 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:12.363 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:12.364 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:12.893 PTT on

M: 2019-03-13 22:43:12.894 P25, TX state = ON

I: 2019-03-13 22:43:12.894 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:13.060 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:43:13.778 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:43:14.498 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W0RAY DMR ID: 311924'

M: 2019-03-13 22:43:15.216 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W0RAY DMR ID: 3119240'

M: 2019-03-13 22:43:15.698 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 1% packet loss, BER: 0.0%

M: 2019-03-13 22:43:15.699 PTT off (keyed for 2806 ms)

M: 2019-03-13 22:43:15.704 P25, TX state = OFF

M: 2019-03-13 22:43:44.719 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:43:44.720 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:43:44.720 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:43:45.221 PTT on

M: 2019-03-13 22:43:45.235 P25, TX state = ON

I: 2019-03-13 22:43:45.235 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:43:46.161 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:46.881 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-03-13 22:43:47.008 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 5% packet loss, BER: 0.0%

M: 2019-03-13 22:43:47.009 PTT off (keyed for 1788 ms)

M: 2019-03-13 22:43:47.014 P25, TX state = OFF

M: 2019-03-13 22:44:00.628 Currently linked repeaters:

M: 2019-03-13 22:44:00.628     W0RAY      (192.168.3.130:42010) 4/120

W: 2019-03-13 22:44:04.998 No response from 31900, unlinking

M: 2019-03-13 22:44:18.316 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:44:18.317 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:44:18.318 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:44:18.819 PTT on

M: 2019-03-13 22:44:18.824 P25, TX state = ON

I: 2019-03-13 22:44:18.824 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:44:18.884 Linked to reflector 31900 by W0RAY

M: 2019-03-13 22:44:18.923 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W0RAY '

M: 2019-03-13 22:44:19.646 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W0RAY DMR ID:'

M: 2019-03-13 22:44:20.123 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 0% packet loss, BER: 0.0%

M: 2019-03-13 22:44:20.123 PTT off (keyed for 1304 ms)

M: 2019-03-13 22:44:20.128 P25, TX state = OFF

M: 2019-03-13 22:45:01.536 Transmission started from W0RAY      (192.168.3.130:42010)

M: 2019-03-13 22:45:01.546 Transmission from W0RAY at W0RAY      to TG 31900

M: 2019-03-13 22:45:05.518 Received end of transmission

M: 2019-03-13 22:45:29.085 DMR Slot 2, received network voice header from W0RAY to TG 3119

I: 2019-03-13 22:45:29.086 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

I: 2019-03-13 22:45:29.086 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240

M: 2019-03-13 22:45:29.587 PTT on

M: 2019-03-13 22:45:29.595 P25, TX state = ON

I: 2019-03-13 22:45:29.595 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

 

M: 2019-03-13 22:45:30.983 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 9% packet loss, BER: 0.0%

M: 2019-03-13 22:45:30.984 PTT off (keyed for 1397 ms)

M: 2019-03-13 22:45:30.989 P25, TX state = OFF

M: 2019-03-13 22:46:00.740 Currently linked repeaters:

M: 2019-03-13 22:46:00.740     W0RAY      (192.168.3.130:42010) 4/120

^C

 

Your synopsis focused mainly on the TalkGroups, 3119 – Brandmeister and 31900 – assigned by me within the P25Repeater and Astro Spectra radios.  I am not clear about what to do with any of this.

 

Are you highlighting these for changes and if so what should I use?  My reading and research of the various fields led me to the values you see.  Too many unclear references to TG, not differentiating between whether to use a Brandmeister TG or a P25 TG.

 

The audio values for agcGain are both -15 in the two A_B.ini parameters.

 

Thank you very much for your valuable time.

 

RayH   w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 11:06 AM
To: main@DVSwitch.groups.io.
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I do not see a transmission from P25, so I'll address DMR -> P25

We see the TX in the MB log here:
M: 2019-03-13 14:27:10.248 DMR Slot 2, received network voice header from W0RAY to TG 3119

In AB_DMR we see this:
I: 2019-03-13 14:27:10.249 Begin TX: src=3119240 rpt=0 dst=3119 slot=2 cc=0

In AB_P25 we see this:
I: 2019-03-13 14:27:10.250 USRP packet type: USRP_TYPE_TEXT (W0RAY) -> 3119240
M: 2019-03-13 14:27:10.806 PTT on

Back to the MB log we see this:
I: 2019-03-13 14:27:10.808 P25, Begin TX: src=3119240 rpt=3119240 dst=31900 slot=2 cc=1

And finally in the P25Reflector log we see:
M: 2019-03-13 14:27:24.942 Transmission from W0RAY at W0RAY      to TG 31900

31900?
Where is that coming from? In AB_P25 we see this:
M: 2019-03-13 14:26:50.193 Setting [AMBE_AUDIO] txTg -> 31900

OK, so that explains the final output TG.

Now, I'm looking at the audio level settings.
In AB_DMR I see this:
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_DMR.ini?

In AB_P25 I see this:
M: 2019-03-13 14:26:50.194 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:50.194 Setting [USRP] agcGain -> -15

What value do you have for agcGain in the AB_P25.ini?

Steve N4IRS


On 3/13/2019 11:44 AM, Ray Harden wrote:

The attached file is the correct one with the same name.  Unfortunately I mistakenly included a file from an earlier run in the former .ZIP.   

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 10:06 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

I don't think the AB logLevel is set at 2.  I don't see a single transmission from P25. If the AB logs do not look like this don't send the files until they do.

I: 2019-03-13 14:26:44.924 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-03-13 14:26:44.924 Created by Mike N4IRR and Steve N4IRS
I: 2019-03-13 14:26:44.924 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 This software is for use on amateur radio networks only,
I: 2019-03-13 14:26:44.924 it is to be used for educational purposes only. Its use on
I: 2019-03-13 14:26:44.924 commercial networks is strictly prohibited.
I: 2019-03-13 14:26:44.924
I: 2019-03-13 14:26:44.924 Analog Bridge is starting
M: 2019-03-13 14:26:44.926 Setting [GENERAL] logLevel -> 2
M: 2019-03-13 14:26:44.926 Setting [GENERAL] exportMetadata -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-03-13 14:26:44.926 Setting [GENERAL] decoderFallBack -> true
M: 2019-03-13 14:26:44.926 Setting [GENERAL] useEmulator -> true
M: 2019-03-13 14:26:44.927 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-03-13 14:26:44.927 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useMicrophone -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] useVox -> false
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxDecay -> 2
M: 2019-03-13 14:26:44.927 Setting [GENERAL] voxTrigger -> 200
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] server -> 127.0.0.1
M: 2019-03-13 14:26:44.927 Setting [AMBE_AUDIO] fromDMRPort -> 31100
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] toDMRPort -> 31103
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] gatewayDmrId -> 311924009
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] repeaterID -> 3119240
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTg -> 31900
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-03-13 14:26:44.928 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-03-13 14:26:44.928 Setting [USRP] server -> 127.0.0.1
M: 2019-03-13 14:26:44.928 Setting [USRP] toASLPort -> 32001
M: 2019-03-13 14:26:44.928 Setting [USRP] fromASLPort -> 34001
M: 2019-03-13 14:26:44.928 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.928 Setting [USRP] agcGain -> -15
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-03-13 14:26:44.929 Setting [USRP] dmrGain -> 0.35
M: 2019-03-13 14:26:44.929 Setting [DV3000] server -> 127.0.0.1
M: 2019-03-13 14:26:44.929 Setting [DV3000] port -> 2460
W: 2019-03-13 14:26:44.929 ioctl reset error
W: 2019-03-13 14:26:44.929 ioctl speed error
W: 2019-03-13 14:26:44.929 ioctl stereo error
W: 2019-03-13 14:26:44.929 ioctl setfmt error
M: 2019-03-13 14:26:44.929 Audio In/Out Device: /dev/null
I: 2019-03-13 14:26:44.929 Open UDP listener on 127.0.0.1:31100
I: 2019-03-13 14:26:44.930 Open USRP on 127.0.0.1:32001
M: 2019-03-13 14:26:44.930 Connecting to DV3000 hardware......
W: 2019-03-13 14:26:45.947 DV3000 not found at 127.0.0.1:2460
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2019-03-13 14:26:46.747 Subscriber IDs loaded: 125115
I: 2019-03-13 14:26:46.747 Default extended metadata <311924009>
I: 2019-03-13 14:26:46.748 Connecting to emulator on host 127.0.0.1:2470
W: 2019-03-13 14:26:46.748 Using software MBE decoder version 1.2.3
W: 2019-03-13 14:26:46.748 Using software OP25 IMBE/AMBE vocoder
I: 2019-03-13 14:26:46.749 Starting Analog_Bridge --> USRP thread
I: 2019-03-13 14:26:46.749 Open UDP listener on 127.0.0.1:34001
I: 2019-03-13 14:26:46.749 Starting USRP --> HB_Bridge thread

On 3/13/2019 10:51 AM, Ray Harden wrote:

A_B logs now have logLevel = 2

 

RayH  w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, March 13, 2019 9:10 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

The AB logs do not contain the settings. Make sure you have
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

Set logLevel to 2 or below and capture all again.

On 3/13/2019 8:58 AM, Ray Harden wrote:

Responding to your request … 5 logs run without the  [  &  ], All Debugs @ 0 this time; keyed TYT-380 DMR radio on Brandmeister TG 3119 first, then a few seconds later the P25 – TG31900 mobile radio >> P25 repeater and its MMDVM-P25-Enabled TG31900 software.  There is a really impressive amount of setup to do this – I have probably missed something!

 

v/r

 

RayH    w0ray

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Tuesday, March 12, 2019 6:20 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Problem Description: No Audio @ P25 radio, No Audio DMR from Bridge P25 <<-->> DMR

 

 


Re: Do we need more subgroups. #poll

Mike KB8JNM
 

Mike, I respectfully understand your position, but not many even understand the difference.

Could we settle on a Bridge Subgroup and at least four of the most popular bridge groups (whatever they are)
and a 3rd group of everything else.
To monitor or sort for help reading all of it in 2/3 groups is not much help for anyone involved.

...mike/kb8jnm

They need to be separated by the search/need pattern. I understand that will change over time.

On 3/13/2019 2:35 PM, Mike Zingman - N4IRR wrote:
A different way to slice this is to have a small set of subgroups that talk about format bridges
AMBE <--> AMBE
AMBE <--> IMBE
DSTAR <--> ANYTHING ELSE


Re: Do we need more subgroups. #poll

Pierre Martel
 

I did not read the whole tread but I have been reading a lot of the group question.

Can I suggest something like 
A group for planification and general use of the software Like what is needed to do such or such bridge or other good parctice.
Then a group for bridging and transcoding problem ( bad port what ini files and where. stuff like that)

Then a group for each specific software.

Just my 2 cents. 

 

Le mer. 13 mars 2019 à 16:17, Steve KC1AWV <smiller@...> a écrit :
I'm kind of leaning towards Mike N4IRR's idea. Though, maybe the groups could be broken up to which programs are needed for the mode/network you're bridging. ASL to BM is easier than say ASL to XLX as it only needs AB and MB, but XLX needs DG for DMR as well. Or BM to DStar, you'd need two MBs and ircDDBGW to go to a REF. There's more than one way to skin a cat here. Maybe start with groups for the input system?

ASL <-> DStar REF
ASL <-> XLX
ASL <-> BM

USRP <-> DStar
USRP <-> XLX
USRP <-> BM

etc...


Re: Do we need more subgroups. #poll

Steve KC1AWV
 

I'm kind of leaning towards Mike N4IRR's idea. Though, maybe the groups could be broken up to which programs are needed for the mode/network you're bridging. ASL to BM is easier than say ASL to XLX as it only needs AB and MB, but XLX needs DG for DMR as well. Or BM to DStar, you'd need two MBs and ircDDBGW to go to a REF. There's more than one way to skin a cat here. Maybe start with groups for the input system?

ASL <-> DStar REF
ASL <-> XLX
ASL <-> BM

USRP <-> DStar
USRP <-> XLX
USRP <-> BM

etc...


Re: Do we need more subgroups. #poll

Steve N4IRS
 

DMR, YSFn, NXDN <-> DMR, YSFn, NXDN
DMR, YSFn, NXDN <-> YSFw, P25
D-Star <-> Any



On 3/13/2019 2:35 PM, Mike Zingman - N4IRR wrote:
A different way to slice this is to have a small set of subgroups that talk about format bridges

AMBE <--> AMBE
AMBE <--> IMBE
DSTAR <--> ANYTHING ELSE


Re: Do we need more subgroups. #poll

Steve N4IRS
 

It makes sense but I see the questions Is NXDN AMBE or IMBE?

On 3/13/2019 2:35 PM, Mike Zingman - N4IRR wrote:
A different way to slice this is to have a small set of subgroups that talk about format bridges

AMBE <--> AMBE
AMBE <--> IMBE
DSTAR <--> ANYTHING ELSE


Re: Do we need more subgroups. #poll

Mike Zingman - N4IRR
 

A different way to slice this is to have a small set of subgroups that talk about format bridges

AMBE <--> AMBE
AMBE <--> IMBE
DSTAR <--> ANYTHING ELSE


Re: Do we need more subgroups. #poll

Steve N4IRS
 

OK, Without ASL below are the base permutations. From that let's eliminate some obvious "I doubt anyone would do this"

Based on Russells comment that most bridges involve DMR
DMR <-> D-Stsr
DMR <-> YSF
DMR <-> NXDN
DMR <-> P25

D-Star <-> YSF
D-Star <-> NXDN
D-Star <-> P25 (I doubt anyone would do this)

YSF <-> NXDN
YSF <-> P25

NXDN <-> P25

BTW, this kinda ignores YSFn vs YSFw

Anyone else care to eliminate a bridge? I'm leaning to create the first four Subgroups and see what happens.

Steve


Re: Do we need more subgroups. #poll

 

I agree assumptions usually get broken fast.

I'm strictly making that comment from what I've seen on this email list and what I've been asked to build for others that reach out to me. AllStar <> DMR being the most common and what builds to the bigger bridges that also include other modes.

destination may not have been the right word as all systems in a bridge is where we expect to hear audio. We this group lays out a bridge flow it usually has a start and end and the end is what i meant by destination in that <> flow.

On Wed, Mar 13, 2019 at 12:57 PM Steve N4IRS <szingman@...> wrote:
I don't agree with the assumption that DMR is involved in every bridge. Does a bridge have a destination?


On 3/13/2019 1:53 PM, Russell, KV4S wrote:
without making it "complicated". The destination would be the topic name.
I think we can assume DMR is the core mode. I don't think I've seen a bridge system someone has worked on that hasn't inluded DMR in the mix with the exception of one i'll talk about later.

I would think subgroups would be Allstar (we already have), main (already have for DMR and general), D-STAR, YSF, P25, NXDN. if you post in those subgroups then the assumption you are tying to bridge dmr to that mode. 

In the case of one i saw was allstar to YSF then you would probably pick YSF group and notate in the subject ASL <> YSF. 

i think this would keep things mostly separated as for topic discussions.

On Wed, Mar 13, 2019 at 12:02 PM Steve N4IRS <szingman@...> wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?

Steve

On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@...> wrote:
So,
A very interesting thing has shown up in the voting so far. Though the majority of votes want separate subgroups, some of the people that answer questions voted to leave things the way they are. 

Steve 



Re: Do we need more subgroups. #poll

Steve N4IRS
 

I don't agree with the assumption that DMR is involved in every bridge. Does a bridge have a destination?


On 3/13/2019 1:53 PM, Russell, KV4S wrote:
without making it "complicated". The destination would be the topic name.
I think we can assume DMR is the core mode. I don't think I've seen a bridge system someone has worked on that hasn't inluded DMR in the mix with the exception of one i'll talk about later.

I would think subgroups would be Allstar (we already have), main (already have for DMR and general), D-STAR, YSF, P25, NXDN. if you post in those subgroups then the assumption you are tying to bridge dmr to that mode. 

In the case of one i saw was allstar to YSF then you would probably pick YSF group and notate in the subject ASL <> YSF. 

i think this would keep things mostly separated as for topic discussions.

On Wed, Mar 13, 2019 at 12:02 PM Steve N4IRS <szingman@...> wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?

Steve

On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@...> wrote:
So,
A very interesting thing has shown up in the voting so far. Though the majority of votes want separate subgroups, some of the people that answer questions voted to leave things the way they are. 

Steve 



Re: Do we need more subgroups. #poll

Jim Gifford - K9AGR
 

That sounds like a reasonable way to handle it to me.

On Mar 13, 2019, at 1:53 PM, Russell, KV4S <russelljthomas@...> wrote:

without making it "complicated". The destination would be the topic name.
I think we can assume DMR is the core mode. I don't think I've seen a bridge system someone has worked on that hasn't inluded DMR in the mix with the exception of one i'll talk about later.

I would think subgroups would be Allstar (we already have), main (already have for DMR and general), D-STAR, YSF, P25, NXDN. if you post in those subgroups then the assumption you are tying to bridge dmr to that mode. 

In the case of one i saw was allstar to YSF then you would probably pick YSF group and notate in the subject ASL <> YSF. 

i think this would keep things mostly separated as for topic discussions.

On Wed, Mar 13, 2019 at 12:02 PM Steve N4IRS <szingman@...> wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?

Steve

On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@...> wrote:
So,
A very interesting thing has shown up in the voting so far. Though the majority of votes want separate subgroups, some of the people that answer questions voted to leave things the way they are. 

Steve 





Re: Do we need more subgroups. #poll

Mike KB8JNM
 

I think that has it as far as I can see except as you mentioned ASL

On 3/13/2019 1:50 PM, Steve N4IRS wrote:
Did I miss any?
D-Star <-> DMR
D-Star <-> YSF
D-Star <-> NXDN
D-Star <-> P25
DMR <-> YSF
DMR <-> NXDN
DMR <-> P25
YSF <-> NXDN
YSF <-> P25
NXDN <-> P25
This is without ASL
On 3/13/2019 1:44 PM, Jim Gifford - K9AGR wrote:
A subgroup per bridge pair could quickly get out of hand.  For N modes, you'd end up with (N * (N-1)) / 2 subgroups.

For 5 modes, that's 10 bridging subgroups.

For 7 modes, you're up to 21 bridging subgroups.

Just off the top of my head, there's Analog, D-Star, YSF Narrow, YSF Wide, DMR, NXDN, and P25, and perhaps more I don't remember or haven't heard of.  That's already 7 modes, or 21 subgroups.

While the topics within would be extremely specific, it would suck having to create all the subgroups.

Personally, I think it might be time for splitting the traffic up some.  But where the dividing lines should fall isn't clear to me yet. Hence my vote for none of the above.

73,
Jim K9AGR

On Mar 13, 2019, at 1:11 PM, Mike KB8JNM <groupio@midnighteng.com <mailto:groupio@midnighteng.com>> wrote:

I would suggest
A separate bridge subgroup for the pair <>


On 3/13/2019 1:02 PM, Steve N4IRS wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?
Steve
On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@msgstor.com <mailto:szingman@msgstor.com><mailto:szingman@msgstor.com>> wrote:

    So,
    A very interesting thing has shown up in the voting so far. Though
    the majority of votes want separate subgroups, some of the people
    that answer questions voted to leave things the way they are.

    Steve


Re: Do we need more subgroups. #poll

 

without making it "complicated". The destination would be the topic name.
I think we can assume DMR is the core mode. I don't think I've seen a bridge system someone has worked on that hasn't inluded DMR in the mix with the exception of one i'll talk about later.

I would think subgroups would be Allstar (we already have), main (already have for DMR and general), D-STAR, YSF, P25, NXDN. if you post in those subgroups then the assumption you are tying to bridge dmr to that mode. 

In the case of one i saw was allstar to YSF then you would probably pick YSF group and notate in the subject ASL <> YSF. 

i think this would keep things mostly separated as for topic discussions.

On Wed, Mar 13, 2019 at 12:02 PM Steve N4IRS <szingman@...> wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?

Steve

On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@...> wrote:
So,
A very interesting thing has shown up in the voting so far. Though the majority of votes want separate subgroups, some of the people that answer questions voted to leave things the way they are. 

Steve 


Re: Do we need more subgroups. #poll

Jim Gifford - K9AGR
 

The (N - 1) accounted for the fact that bridges work in 2 directions.  Otherwise it would be N*N / 2.

On Mar 13, 2019, at 1:50 PM, Mike KB8JNM <groupio@...> wrote:

I would understand that it is a number of subgroups, but I don't think as many as you state because you are counting some twice.

DMR <> YSF would include YSF <> DMR

But in any case, a BRIDGING subgroup might be in order as a start till more is sorted out.

On 3/13/2019 1:44 PM, Jim Gifford - K9AGR wrote:
A subgroup per bridge pair could quickly get out of hand.  For N modes, you'd end up with (N * (N-1)) / 2 subgroups.
For 5 modes, that's 10 bridging subgroups.
For 7 modes, you're up to 21 bridging subgroups.
Just off the top of my head, there's Analog, D-Star, YSF Narrow, YSF Wide, DMR, NXDN, and P25, and perhaps more I don't remember or haven't heard of.  That's already 7 modes, or 21 subgroups.
While the topics within would be extremely specific, it would suck having to create all the subgroups.
Personally, I think it might be time for splitting the traffic up some.  But where the dividing lines should fall isn't clear to me yet. Hence my vote for none of the above.
73,
Jim K9AGR
On Mar 13, 2019, at 1:11 PM, Mike KB8JNM <groupio@...> wrote:

I would suggest
A separate bridge subgroup for the pair <>


On 3/13/2019 1:02 PM, Steve N4IRS wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?
Steve
On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@... <mailto:szingman@...> <mailto:szingman@... <mailto:szingman@...>>> wrote:

    So,
    A very interesting thing has shown up in the voting so far. Though
    the majority of votes want separate subgroups, some of the people
    that answer questions voted to leave things the way they are.

    Steve






Re: Do we need more subgroups. #poll

Steve N4IRS
 

Did I miss any?
D-Star <-> DMR
D-Star <-> YSF
D-Star <-> NXDN
D-Star <-> P25

DMR <-> YSF
DMR <-> NXDN
DMR <-> P25

YSF <-> NXDN
YSF <-> P25

NXDN <-> P25

This is without ASL

On 3/13/2019 1:44 PM, Jim Gifford - K9AGR wrote:
A subgroup per bridge pair could quickly get out of hand.  For N modes, you'd end up with (N * (N-1)) / 2 subgroups.

For 5 modes, that's 10 bridging subgroups.

For 7 modes, you're up to 21 bridging subgroups.

Just off the top of my head, there's Analog, D-Star, YSF Narrow, YSF Wide, DMR, NXDN, and P25, and perhaps more I don't remember or haven't heard of.  That's already 7 modes, or 21 subgroups.

While the topics within would be extremely specific, it would suck having to create all the subgroups.

Personally, I think it might be time for splitting the traffic up some.  But where the dividing lines should fall isn't clear to me yet. Hence my vote for none of the above.

73,
Jim K9AGR

On Mar 13, 2019, at 1:11 PM, Mike KB8JNM <groupio@...> wrote:

I would suggest
A separate bridge subgroup for the pair <>


On 3/13/2019 1:02 PM, Steve N4IRS wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?
Steve
On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@... <mailto:szingman@...>> wrote:

    So,
    A very interesting thing has shown up in the voting so far. Though
    the majority of votes want separate subgroups, some of the people
    that answer questions voted to leave things the way they are.

    Steve





Re: Do we need more subgroups. #poll

Mike KB8JNM
 

I would understand that it is a number of subgroups, but I don't think as many as you state because you are counting some twice.

DMR <> YSF would include YSF <> DMR

But in any case, a BRIDGING subgroup might be in order as a start till more is sorted out.

On 3/13/2019 1:44 PM, Jim Gifford - K9AGR wrote:
A subgroup per bridge pair could quickly get out of hand. For N modes, you'd end up with (N * (N-1)) / 2 subgroups.
For 5 modes, that's 10 bridging subgroups.
For 7 modes, you're up to 21 bridging subgroups.
Just off the top of my head, there's Analog, D-Star, YSF Narrow, YSF Wide, DMR, NXDN, and P25, and perhaps more I don't remember or haven't heard of. That's already 7 modes, or 21 subgroups.
While the topics within would be extremely specific, it would suck having to create all the subgroups.
Personally, I think it might be time for splitting the traffic up some. But where the dividing lines should fall isn't clear to me yet. Hence my vote for none of the above.
73,
Jim K9AGR

On Mar 13, 2019, at 1:11 PM, Mike KB8JNM <groupio@midnighteng.com> wrote:

I would suggest
A separate bridge subgroup for the pair <>


On 3/13/2019 1:02 PM, Steve N4IRS wrote:
So the question becomes, I want to build a DMR <-> D-Star bridge, what subgroup do I use? DMR? D-Star?
Steve
On 3/13/2019 9:08 AM, Russell, KV4S wrote:
somehow i missed it too i must have marked everything read when i got a backlog of messages from being away a few days......

I'm very much in favor of the subgroups, it makes things easier to ready when you know the topic ahead of time vs all being in one big email list.

Example Allstar subgroup vs main.

On Tue, Mar 12, 2019 at 6:31 PM Steve N4IRS <szingman@msgstor.com <mailto:szingman@msgstor.com> <mailto:szingman@msgstor.com <mailto:szingman@msgstor.com>>> wrote:

So,
A very interesting thing has shown up in the voting so far. Though
the majority of votes want separate subgroups, some of the people
that answer questions voted to leave things the way they are.

Steve

5741 - 5760 of 9288