Date   
#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

Re: ASL_node_list.txt

Mike Zingman - N4IRR
 

And yes you did misunderstand.

Nodes in  the database (node_list.txt) are preceded by a *2 when invoked from the "Nodes" menu or using the long press for the first 10
Nodes in the "Macro" menu, accessed from the long press of * or the "Macro" dropdown (like Connect to Node 2600) are dialed as is
Nodes in the ad-hoc menu, long press * after loading a new menu with sendtext from the ASL node are dialed as is.

So, If you add to the database, postfix it with *30
If you add it anywhere else, prefix it with *3 to connect in transmit mode.

Re: ASL_node_list.txt

Mike Zingman - N4IRR
 

Sorry, ment *30

so a string like *22100*30 would dial node 2100 in RX mode then change over to TX.  DVSM supplies the *2 so you would not need that in your database.

Re: ASL_node_list.txt

Tom Corcoran
 

I tried your suggestion … but still getting rx only.

tried 
42328 *3|VE3KKF|Baslam Lake

and also 
42328*3|VE3KKF|Baslam Lake

did I misunderstand your recommendation?
--
Tom VE3NY

Re: ircddbgateway install command line only

va3dxv
 

Thank you Steve, yep that's what I've been doing here too. libwxbase3.0-dev is installed. Building on rasbian 4.9.8

the previous posted output was of the g4lkx compile. this is of dl5di's, failing at the same file :(

GUICommon/AddressTextCtrl.cpp:21:111: error: ‘wxSize’ does not name a type
 w* parent, int id, const wxString& value, const wxPoint& pos, const wxSize& size, long style) :
                                                                     ^~~~~~
Makefile:2788: recipe for target 'GUICommon/libGUICommon_a-AddressTextCtrl.o' failed
make: *** [GUICommon/libGUICommon_a-AddressTextCtrl.o] Error 1

Re: ASL_node_list.txt

Mike Zingman - N4IRR
 

Hmmm, I have not look at that code  in a while.  Yes, I did make the decision to use monitor  rather than transceive.  You can just do a *3 at the end of the node number to fix it I guess.  The proper solution is to have a dial prefix for ASL in the account setup, but that will not be something I do in the short term.  
If you use the AD-Hoc menu it should not add a prefix, so I might suggest that is a good solution for a while

Re: attenuating USRP gain post-AGC processing

Mike Zingman - N4IRR
 

I added the gain block after the AGC processing, so this should address your needs.  Steve will release soon as there are some other changes in the pipeline as well.

Re: DVSWITCH in Pi Zero

ea7jcl@...
 

Perfect, this is the solution.
 
Many thanks

Re: Where is the DVSM_Update.sh scripts?

EA5GVK Joaquin
 

Ok. Thx.


El lun., 1 jun. 2020 20:16, Steve N4IRS <szingman@...> escribió:
I have not decided it I'm going to use that systemd unit file or not.
<https://github.com/DVSwitch/DVSwitch-System-Builder/blob/master/Directories/usr/local/sbin/DVSM_Update.sh>

On 6/1/2020 2:13 PM, EA5GVK Joaquin wrote:
Steve please, where is the DVSM_Update.sh script, in the new service update_data_files.system
Thank you.

Re: ircddbgateway install command line only

Steve N4IRS
 

I build the G4LKX repo with:
apt-get install libwxbase3.0-dev
make
I have built on arm and intel/amd.

Steve N4IRS

On 6/1/2020 2:28 PM, va3dxv wrote:

Hello I realize it may be off topic for this group but... How are you getting ircddbgateway to compile with no X/GUI environment?

I do have wxwidgets base installed. I've tried the latest source direct from g4klx and also the old dl5di/opendv fork. In both cases the compile gets about half done then fails and complains as soon as it gets to compiling stuff in GUICommon.

The configure script for the dl4di fork completes without error using --without-gui, but when I compile it, I get the same errors that I get with the g4klx code. I don't understand why it would even try to build the GUICommon stuff

Am I missing something? Thank You


make[1]: Leaving directory '/home/repeater/ircDDBGateway/ircDDBGateway'
make -C GUICommon
make[1]: Entering directory '/home/repeater/ircDDBGateway/GUICommon'
g++ -O2 -Wall -I/usr/lib/arm-linux-gnueabihf/wx/include/base-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -pthread -DLOG_DIR='"/var/log"' -DCONF_DIR='"/etc"' -DDATA_DIR='"/usr/share/ircddbgateway"' -g -D_DEBUG -I../Common -c -o AddressTextCtrl.o AddressTextCtrl.cpp
In file included from AddressTextCtrl.h:24:0,
                 from AddressTextCtrl.cpp:19:
RestrictedTextCtrl.h:24:47: error: expected class-name before ‘{’ token
 class CRestrictedTextCtrl : public wxTextCtrl {
                                               ^
Makefile:13: recipe for target 'AddressTextCtrl.o' failed

Re: DVSWITCH in Pi Zero

Mike Zingman - N4IRR
 

Run it with quem-arm

qemu-arm /opt/md380-emu -S 2470 &
 

Re: ircddbgateway install command line only

va3dxv
 

Hello I realize it may be off topic for this group but... How are you getting ircddbgateway to compile with no X/GUI environment?

I do have wxwidgets base installed. I've tried the latest source direct from g4klx and also the old dl5di/opendv fork. In both cases the compile gets about half done then fails and complains as soon as it gets to compiling stuff in GUICommon.

The configure script for the dl4di fork completes without error using --without-gui, but when I compile it, I get the same errors that I get with the g4klx code. I don't understand why it would even try to build the GUICommon stuff

Am I missing something? Thank You


make[1]: Leaving directory '/home/repeater/ircDDBGateway/ircDDBGateway'
make -C GUICommon
make[1]: Entering directory '/home/repeater/ircDDBGateway/GUICommon'
g++ -O2 -Wall -I/usr/lib/arm-linux-gnueabihf/wx/include/base-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -pthread -DLOG_DIR='"/var/log"' -DCONF_DIR='"/etc"' -DDATA_DIR='"/usr/share/ircddbgateway"' -g -D_DEBUG -I../Common -c -o AddressTextCtrl.o AddressTextCtrl.cpp
In file included from AddressTextCtrl.h:24:0,
                 from AddressTextCtrl.cpp:19:
RestrictedTextCtrl.h:24:47: error: expected class-name before ‘{’ token
 class CRestrictedTextCtrl : public wxTextCtrl {
                                               ^
Makefile:13: recipe for target 'AddressTextCtrl.o' failed

Re: Analog Bridge Binds to the same port

Matthew 2E0SIP
 

Awesome, thanks all!

Re: Analog Bridge Binds to the same port

Mike Zingman - N4IRR
 

I have addressed the issue.  We will need to test in-house for a while to make sure it is solid (more changes than a simple listener).  Steve will release when it is solid

Re: Where is the DVSM_Update.sh scripts?

Steve N4IRS
 

I have not decided it I'm going to use that systemd unit file or not.
<https://github.com/DVSwitch/DVSwitch-System-Builder/blob/master/Directories/usr/local/sbin/DVSM_Update.sh>

On 6/1/2020 2:13 PM, EA5GVK Joaquin wrote:
Steve please, where is the DVSM_Update.sh script, in the new service update_data_files.system
Thank you.

Where is the DVSM_Update.sh scripts?

EA5GVK Joaquin
 

Steve please, where is the DVSM_Update.sh script, in the new service update_data_files.system
Thank you.

DVSWITCH in Pi Zero

ea7jcl@...
 

If I try to run dvswitch on a pi zero, mmdvm_bridge and analog_bridge, they work apparently fine, but the md380-emu boots, but upon starting the conversion it returns an error.
 
root@raspberrypi:/opt/md380-emu# ./md380-emu -v -S 2470
Listening on port 2470, entering while loop
data ready
got 7 bytes
Illegal instruction
 
Could it be because of the pi zero processor? any ideas?
 
Thanks 

Re: Analog Bridge Binds to the same port

 

If you are running the ambeserver on the same device.

address = 127.0.0.1                   ; IP address of AMBEServer
rxPort = 2460                         ; Port of AMBEServer
address = /dev/ttyUSB0              ; Device of DV3000U on this machine
baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
serial = false                       ; Use serial=true for direct connect or serial=false for AMBEServer
I found that I needed the bottom three lines as well.