Date   

Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

I think it will send "ID" if you comment it out.

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

Make sure the lines starting with idrecording and idtalkover are either commented out or don't exist in /etc/asterisk/rpt.conf under the stanza for the node where your DMR bridge lives. You may also want to make sure duplex=0 and telemdefault=0, unless you have a special case, as I do.


On 12/27/2020 2:23 PM, Mike KB8JNM wrote:

Check your radio programming for the channel

On 12/27/2020 2:17 PM, Frank C. D'Amato wrote:
I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Mike KB8JNM
 

Check your radio programming for the channel

On 12/27/2020 2:17 PM, Frank C. D'Amato wrote:
I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Re: DVSwitch running on 2nd Raspberry Pi

Frank C. D'Amato
 

I decided i'm not gonna run the pyUC


WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Frank C. D'Amato
 

I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Restarting DVSwitch Services

g8ptn@...
 

Hi,

I have noticed that when restarting services via the "dvs" menu “Restart DVSwitch Services” or using the “Drop Dynamic TGs” in the DVSM App, the DMR server always returns to a particular server.


When restarting DVSwitch services, what determines what DMR server is selected?

Regards,
   Dave


Re: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

Dave M0UPM
 

Corey, I have messaged him as much in a private mail. Dave M0UPM BM UK Admin 


On 26 Dec 2020, at 22:31, Corey Dean N3FE <n3fe@...> wrote:

Brandmeister prefers you to directly work with the master and do a true xlx connection as it uses the xlx protocol directly.


On Dec 26, 2020, at 2:06 PM, craig.jump via groups.io <craig.jump@...> wrote:

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM
<MMDVM_BM_BRIDGEtoXLX.zip>


Re: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

Corey Dean N3FE
 

Brandmeister prefers you to directly work with the master and do a true xlx connection as it uses the xlx protocol directly.


On Dec 26, 2020, at 2:06 PM, craig.jump via groups.io <craig.jump@...> wrote:

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM
<MMDVM_BM_BRIDGEtoXLX.zip>


Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

craig.jump@...
 

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM


Re: DVSwitch running on 2nd Raspberry Pi

Ken Kayser
 

Frank.  Anytime you try and execute a command from the current directory, you must proceed it with a ./ so you should enter ./pyUC.py    Also, Python may not be in your path.  Try python3 pyUC.py.  Let us know what happens


Re: DVSM APP server pool

Ralf, DC9NYC
 

I am sorry - the IP address is: ...

87.191.190.207, Port 50111
87.191.190.207, Port 50112
87.191.190.207, Port 50113

Ralf, DC9NYC


Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

fabiobassa
 

Sure Steve I will post there too and ty again for wonderfull work done on those digital systems

73 ' s


Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

Steve N4IRS
 

I suggest you post this information in the HBlink subgroup <https://dvswitch.groups.io/g/HBlink> Where more HBlink users will see it.

Steve N4IRS

On 12/26/20 6:45 AM, fabiobassa wrote:

Hello Bob, thank you for kind replay.

unfortunately Parrot documentation on hblink3 is fragmented , a piece here, a piece there so a bit unconfortable to follow the puzzle

On my radio of course the parrot is a group call and I can engage the parrot, what is frustrating  WAS the wrong audio coming back

I  found another polish man talking about parrot  on hblink3 and he says that first is necessary start the parrot service itself , otherwise no parrot service on board

So it ise necessary have a parrot.service or start by hand calling

/usr/bin/python3 /srv/HBlink3-main/HBlink3/playback.py  -c /srv/HBlink3-main/HBlink3/playback.cfg

that is my relative path.

Following the guidance to have a parrot.service , in facts,  now the parrot is working succesfully

Was just the lack of a service

thanks again , 73's Marco IZ8XOH



Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

fabiobassa
 

Hello Bob, thank you for kind replay.

unfortunately Parrot documentation on hblink3 is fragmented , a piece here, a piece there so a bit unconfortable to follow the puzzle

On my radio of course the parrot is a group call and I can engage the parrot, what is frustrating  WAS the wrong audio coming back

I  found another polish man talking about parrot  on hblink3 and he says that first is necessary start the parrot service itself , otherwise no parrot service on board

So it ise necessary have a parrot.service or start by hand calling

/usr/bin/python3 /srv/HBlink3-main/HBlink3/playback.py  -c /srv/HBlink3-main/HBlink3/playback.cfg

that is my relative path.

Following the guidance to have a parrot.service , in facts,  now the parrot is working succesfully

Was just the lack of a service

thanks again , 73's Marco IZ8XOH


Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

Bob KK6RQ
 

Dunno if this applies, but on our HBLink server Parrot 9990 has to be a *group* call... (I'm not the person maintaining it so I can't expand on that; I just know that's how it is...)

KK6RQ

On Sat, Dec 26, 2020, 4:01 AM fabiobassa <fabiobassa@...> wrote:

[Edited Message Follows]

Hello all,
following many tutorials and hows to, and studying and again studying I succesfully manage to install hblink on a amhf rockchip processor board. It starts and also dashboard is working fine.

But now I have a problem I'm not able to debug properly.

Let descrive my setup:
have a economic chinese clone hotspot simplex mounted on another armhf board and running MMDVMhost. Also have 2 ini files, one with registration to Italy brandmeiseter, another ini registering on lan local hblink. I start then with ./mmdvmhost /home/myhome/brandmeister.ini or ./mmdvmhost /home/myhome/hblink.ini so I can follow on screnn what is going on.

Scenario GOOD : I register into brandmeister , call the parrot 9990 and hear the talkback:

M: 2020-12-25 23:16:26.089 DMR, Logged into the master successfully
M: 2020-12-25 23:16:34.111 DMR Slot 2, received RF voice header from xxxxxx to 9990
M: 2020-12-25 23:16:37.891 DMR Slot 2, received RF end of voice transmission from  xxxxxx to 9990, 3.6 seconds, BER: 0.9%
M: 2020-12-25 23:16:41.056 DMR Slot 2, received network voice header from 9990 to xxxxxx
M: 2020-12-25 23:16:44.663 DMR Slot 2, received network end of voice transmission from 9990 to xxxxxx, 3.7 seconds, 0% packet loss, BER: 0.2%

Scenario BAD : I log into local hblink , call the parrot and a lot of error coming out

M: 2020-12-25 23:27:30.015 DMR, Logged into the master successfullE: 2020-12-25 23:27:59.324

DMR Slot 2, overflow in the DMR slot RF queue ( many many of these)
M: 2020-12-25 23:28:00.822 DMR Slot 2, network watchdog has expired, 7.1 seconds, 69% packet loss, BER: 0.2% ( and voice is not intellegible)

 

By searching on Google this  same error It landed me to MAYBE a problem with tcxo on my hotspot hat  but here come questions:

Why the same hardware is working on brendmeister network and not working on local hblink? If was a tcxo problem it shouldn't have worked on neither

What can I use to debug the underlaying problem or, if we do a sort od meeting, could anyone check from outside with different hardware if all the stuff are correct? Of course will give a public ip and open port and setup a momentary password for tests.

 

Thank you in advance for replays, 73's Marco iz8xoh

EDIT : I read a topic on 05/08/19 that says "
Parrot is not (yet) ported to python3"

Is that the reason ?


Re: DVSwitch running on 2nd Raspberry Pi

Steve N4IRS
 

Frank,
pyUC is a client program written in Python3. It requires a system with a graphic interface (Linux window manager, Microsoft Windows, Apple MAC. it is not intended to run on the server. That is not to say it CAN'T be run on the server. I just want you to understand the program.

When you run a Linux program it either must be in you path or you must explicitly tell Linux the full path. Since pyUC is a python program run it with python3 pyUC.py.

The md380-emulator is installed and set to start on boot by the image or install script.

To connect your DVSwitch Server to your HAMVOIP node:

Add a private node to HAMVOIP. Use this as a guide for the node stanza <https://github.com/DVSwitch/Analog_Bridge/blob/master/ASL/rpt.conf.txt>
instead of setting the rxchannel to 127.0.0.1, set it to the address of your DVSwitch Server
Once you have the private node setup and working on HAMVOIP change the [USRP] stanza in Analog_Bridge.ini:
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 1.10                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_UNITY                  ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)


Set the address above to the IP address of your HAMVOIP node.

Steve N4IRS 

On 12/25/20 6:51 PM, Frank C. D'Amato wrote:
I set up a Raspberry Pi last week with Hamvoip.  The Allstar Node is up and running and RF is connected.  It has a private node 1999 also.

I installed DVSwitch on the second Pi (No ALS)

I followed the DVSwitch Installation and User Guide v1.61.pdf instructions but am stuck at the pyUC

I unzipped the USRP Client and copied it to home/pyUC

I ran the following command;
sudo apt-get install python3-pyaudio
sudo apt-get install portaudio19-dev
sudo apt-get install python3-pil.imagetk

I edited the pyUC.ini file
and did a sudo chmod 775 pyUC.py

When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found"
Why would I get this error?

My MMDVM_Bridge shows my callsign when I key my radio to the designated TG
My ANALOG_Bridge shows my callsign when I key my radio to the designated TG

I don't see any instructions on setting up the MD-380 Emulator, or how to finally connect the DVSwitch to my Hamvoip Allstar Node located at 192.168.1.9 on my network

Please help






Re: DVSwitch running on 2nd Raspberry Pi

larry_n7fm
 

Frank which directory are you issuing the pyUC.py command from? If the same directory as the one holding pyUC.py script try ./pyUC.py.

Otherwise make sure the path is know.

Larry - N7FM

On 12/25/20 3:51 PM, Frank C. D'Amato wrote:
When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found"
Why would I get this error?


DVSwitch running on 2nd Raspberry Pi

Frank C. D'Amato
 

I set up a Raspberry Pi last week with Hamvoip.  The Allstar Node is up and running and RF is connected.  It has a private node 1999 also.

I installed DVSwitch on the second Pi (No ALS)

I followed the DVSwitch Installation and User Guide v1.61.pdf instructions but am stuck at the pyUC

I unzipped the USRP Client and copied it to home/pyUC

I ran the following command;
sudo apt-get install python3-pyaudio
sudo apt-get install portaudio19-dev
sudo apt-get install python3-pil.imagetk

I edited the pyUC.ini file
and did a sudo chmod 775 pyUC.py

When I try to execute pyUC.py (by typing pyUC.py) I get "a -bash: pyUC.py: command not found"
Why would I get this error?

My MMDVM_Bridge shows my callsign when I key my radio to the designated TG
My ANALOG_Bridge shows my callsign when I key my radio to the designated TG

I don't see any instructions on setting up the MD-380 Emulator, or how to finally connect the DVSwitch to my Hamvoip Allstar Node located at 192.168.1.9 on my network

Please help




741 - 760 of 8708