Date   

Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Hi Steve,

I have tried running only the 2 instances of AB and it happens when I send the dvswitch tune command. The logs I included had no MB running at all. Other tests I performed were only running the AB_P25 and then the AB_DMR along with the rest of the system and then when I ran the dvswitch command or keyed up on the radio there was no spamming of info packets. 
 
Today I though I would leave it running for a while after issuing the dvswitch tune 9999 (disconnect) running for 3 hours at 100 CPU. 

Does AB pull any setting from the DVswitch.ini file in the MB directory? 

I'll pull the Configs for those when I get to the PC tomorrow.

Thanks
Tim vk3ftzd


Re: Some questions about dvswitch.sh and Analog_Bridge

Steve N4IRS
 

Tim,
You are correct, suppressing the log does no good. We need to know what is going on.  Lets start with the DMR side of the bridge. Turn off AB_P25. I assume you are running one instance of MB. So in MB.ini disable P25 and P25 networking.
Set the log level to 1 and capture the AB and MB logs. I would also like to see your MB.ini and dvswitch.ini.

Steve N4IRS

On 6/4/2020 5:35 AM, Tim Payne wrote:
Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.

Hiding the alerts doesn't necessarily mean it fixes the problem. You say you use the logs yourself. Do you see this in your logs? Is it normal to have this happening?


Re: Some questions about dvswitch.sh and Analog_Bridge

 

Hello Tim

I never look at logs.
Just look at the info on the screen.
Can see whats going on in real time.
Also see whats gone down then just restart the software.

There is always info passing back and forth from Analog_Bridge.
It will be the transcoding from dmr to p25 thats using the cpu not the info.


Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.

Hiding the alerts doesn't necessarily mean it fixes the problem. You say you use the logs yourself. Do you see this in your logs? Is it normal to have this happening?


Re: Some questions about dvswitch.sh and Analog_Bridge

 

In the Analog_Bridge.ini

loglevel = 2 you could change it to 0

I never change it as I use this info to see whats going on. 
As I run in terminal windows the info from the logs act like a dashboard for me.
Tx begin, Tx end, callsigns etc.


Re: #analog_bridge #analog_bridge

andrew delgado
 

i did stop the ambe server here is the logs. same error on port 31100 will close upon sending the marco ^DMR mode

I: 2020-06-04 03:23:37.362 Tune macro: *DMR will invoke "/opt/Analog_Bridge/dvswitch.sh mode DMR"
I: 2020-06-04 03:23:37.548 rxport=: 30000
M: 2020-06-04 03:23:37.549 TLV rx socket reopened for 127.0.0.1:30000
I: 2020-06-04 03:23:38.862 MESSAGE packet sent to USRP client: Setting mode to DMR
I: 2020-06-04 03:23:38.937 ambeMode = DMR, size = 72
M: 2020-06-04 03:23:38.937 Connecting to DV3000 hardware......
M: 2020-06-04 03:23:38.948 Begin DV3000 decode
I: 2020-06-04 03:23:39.009 txport=: 31103
I: 2020-06-04 03:23:39.102 rxport=: 31100
E: 2020-06-04 03:23:39.103 Can not bind port 31100, error code = 98 (Address already in use)
M: 2020-06-04 03:23:39.103 TLV rx socket reopened for 127.0.0.1:31100
I: 2020-06-04 03:23:40.345 Macro result was 0


Re: #analog_bridge #analog_bridge

andrew delgado
 

Yes Mike, Im running the stick at the same host using pi3,

my problem is when i issue the DMR mode @ Dvswitch mobile client the error pertaining to port 31100 will close. and will not receive audio from mobile phone ,and tx from mobile phone is okay.

I: 2020-06-04 03:14:03.590 ambeMode = DMR, size = 72
M: 2020-06-04 03:14:03.591 Connecting to DV3000 hardware......
E: 2020-06-04 03:14:03.591 Can not bind port 2460, error code = 98 (Address already in use)
M: 2020-06-04 03:14:03.625 Begin DV3000 decode
I: 2020-06-04 03:14:03.670 txport=: 31103
I: 2020-06-04 03:14:03.742 rxport=: 31100
E: 2020-06-04 03:14:03.743 Can not bind port 31100, error code = 98 (Address already in use)
M: 2020-06-04 03:14:03.743 TLV rx socket reopened for 127.0.0.1:31100
I: 2020-06-04 03:14:04.911 Macro result was 0


Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Hey guys, 

Still plotting on with this spamming of "INFO packet sent to USRP client" in my logs. it seems to be related to the 2 instances of AB. 

My setup is HBlink Master2 ----> MB -----> AB_DMR -----> AB_P25 ------> MB -------> P25Gateway.

I have killed every other process for my setup and only included the 2 for AB. I have checked ports are correct and nothing looping back into itself or into another part. I have even changed the ports away from the port mappings in the example in case something else was causing this. Still scratching my head. I have uploaded my configs and logs in case anyone has the time to look and give a second opinion. 

Thanks
Cheers 73's
Tim VK3FTZD


Re: #analog_bridge #analog_bridge

Mike Zingman - N4IRR
 

Andrew, 

By the error you are seeing I have to assume you are running AMBEServer on the same machine as Analog_Bridge is running on.  If this is so, you can just run the DV3000 (or other stick) directly.
If for some reason you need to run AMBEServer, you can ignore the message (it is fixed in a future release of AB)

Mike N4IRR


Re: #analog_bridge #analog_bridge

andrew delgado
 

 HI Ernie,

I only have one instance for analog and mmdvm bridge this is right after install and configuration from the pdf documentation posted here.

Regards,
Andrew


Re: ARM IMAGE

Scott Evans
 

Hamvoip is based on Arch not Debian! So you need to use the correct package manager.

pacman -Sy package_name

This will install packages in Arch, if you need further information about pacman (not the arcade game!) then type...

man pacman

This will print out the manual to screen so that you can read it.

Apt is Debian's package management as yum is for redhat/fedora based systems.

Cheers


Re: ARM IMAGE

Pete Fierro
 

How were you able to get DV Switch on hamvoip?

    I did "apt-get install dvswitch -y" at the shell& got this message

     apt-get command not found


On Wed, Jun 3, 2020 at 11:54, W8DSB
<w8dsb@...> wrote:
Yes, I currently have DVSwitch installed on a HAMVOIP image and that allows allstar to DMR. I am sure it will do more but I have not looked into anything else just yet. The issue is even with a DV3000 USB installed the DMR to FM is not as good as it should be. Not like some of these XLX installs that just sound perfect.


Re: ARM IMAGE

W8DSB
 

Yes, I currently have DVSwitch installed on a HAMVOIP image and that allows allstar to DMR. I am sure it will do more but I have not looked into anything else just yet. The issue is even with a DV3000 USB installed the DMR to FM is not as good as it should be. Not like some of these XLX installs that just sound perfect.


Re: ARM IMAGE

Steve N4IRS
 

On second thought, Will you be connecting the AllStar node to a analog radio?

Steve N4IRS

On 6/3/2020 10:05 AM, W8DSB wrote:
Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.


Re: ARM IMAGE

Steve N4IRS
 

Not yet.....

On 6/3/2020 10:05 AM, W8DSB wrote:
Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.


ARM IMAGE

W8DSB
 

Is there a ARM image available (PI 4) that has ASL, DVSWitch already installed? I have made a few now using HAMVOIP and DVSwitch but the ASL to DMR is only so so even with a DV3000 USB dongle. Hoping to find something that works better.


Re: #analog_bridge #analog_bridge

 

You may have another Analoge_Bridge running.
MMDVM_Bridge and Analoge_Bridge have usually been installed to start up when your device is restarted.
I get caught out myself. I like running them in terminal windows. Find it easier to fault find.
sudo systemctl stop analog_bridge
sudo systemctl stop mmdvm_bridge


#analog_bridge #analog_bridge

andrew delgado
 
Edited

Hi All,

Can you help me with the error below? it seems that theres an error on port when clicking the marco<>Mode Select <> DMR on mobile phone
port 31100 will close.

I: 2020-06-03 04:51:38.416 MESSAGE packet sent to USRP client: Setting mode to DMR
I: 2020-06-03 04:51:38.489 ambeMode = DMR, size = 72
M: 2020-06-03 04:51:38.489 Connecting to DV3000 hardware......
E: 2020-06-03 04:51:38.489 Can not bind port 2460, error code = 98 (Address already in use)
M: 2020-06-03 04:51:38.533 Begin DV3000 decode
I: 2020-06-03 04:51:38.568 txport=: 31103
I: 2020-06-03 04:51:38.669 rxport=: 31100
E: 2020-06-03 04:51:38.670 Can not bind port 31100, error code = 98 (Address already in use)
M: 2020-06-03 04:51:38.670 TLV rx socket reopened for 127.0.0.1:31100
I: 2020-06-03 04:51:39.905 Macro result was 0

Thanks!
Andrew 73!


Re: ASL_node_list.txt

Tom Corcoran
 

Works great Mike. tnx a lot. will be a big benefit when mobiling. FWIW, to make testing and loading simpler, I created a much smaller node_list.txt file - only a dozen entries instead of the 15K standard.
--
Tom VE3NY


Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Evening all,

I am pretty new to the MMDVM_Bridge software and was trying have a bridge from private hblink server to p25 networks. to do this i was trying HBlink ----> DMR2YSF -----> YSF2P25 -----> P25Gateway -----> P25Parrot. this method was not working. I could see traffic going one way but not back the other way.

Then I found this software and got it working. But i have a couple of questions. 
1st is about the dvswitch.sh script. I have a small python script that looks at the hblink logs and runs the dvswitch command to "tune" the correct talk group. but the only way i can make sure that it only changes the P25 instance of Analog_Bridge is to make sure the p25 instance is started after the DMR instance. is there another way?

2nd question is. I keep getting lots of info packet lines in my Analog_Bridge log files. this puts CPU usage up to 90%. Server starts up normally and nothing much in logs about it. But as soon as there is data, even just change talkgroup with dvswitch.sh, then the 2 instances of Analog_Bridge just spam each other and cpu load hits near max. This doesnt stop until I have killed one of the instances. Is this normal? or something wrong with configuration files? should I be running on a faster PC? The PC is a 1.6GHz Atom CPU and 2GB RAM with Ubuntu Server 18.04 running.

Thanks and 73's
Tim VK3FTZD

2621 - 2640 of 9149