ASL<>Analog_Bridge<>HBlink not working
Steve Siesel [K4KSA]
All,
I’ve just upgraded to the latest Analog Bridge and HBLink from github and I am having some issues and need some help. Originally I was thinking my DV3000 was not working but after doing AMBEtest4.py it came back successful. ASL does talk to analog_bridge…I see can see the PTT on and off:
M: 2018-04-14 20:54:02.109 PTT on M: 2018-04-14 20:54:07.288 PTT off (keyed for 5179 ms)
However I don’t see anything in the HBlink screen. Also I don’t see DMR transmissions made on the talkgroup:
INFO 2018-04-14 17:01:57,649 (REPEATER-1) Sending login request to master 74.91.114.19:62031 DEBUG 2018-04-14 17:01:57,650 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x764d3da0> INFO 2018-04-14 17:01:57,690 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2715672343 INFO 2018-04-14 17:01:57,737 (REPEATER-1) Repeater Authentication Accepted INFO 2018-04-14 17:01:57,739 (REPEATER-1) Repeater Configuration Sent INFO 2018-04-14 17:01:57,785 (REPEATER-1) Repeater Configuration Accepted INFO 2018-04-14 17:01:57,786 (REPEATER-1) Connection to Master Completed DEBUG 2018-04-14 17:02:02,652 (REPEATER-1) Client maintenance loop started DEBUG 2018-04-14 17:02:02,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0 DEBUG 2018-04-14 17:02:02,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1 DEBUG 2018-04-14 17:02:07,652 (REPEATER-1) Client maintenance loop started DEBUG 2018-04-14 17:02:07,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0 DEBUG 2018-04-14 17:02:07,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 2
Here is my Analog_bridge.ini:
; Analog_Bridge configuration file. ; This file should be placed in either /etc or it can be ; supplied as a path on the Analog_Bridge command line.
; General Section describes settings for Analog_Bridge itself. ; For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated [GENERAL] ; Audio devices are normally not needed when in gateway service. These devices should ; only be set when local monitor or dongle modes are required.
logLevel = 2 ; Show messages and above outputAudioDevice = /dev/null ; Audio device /dev/null, /dev/dsp1, portaudio, etc inputAudioDevice = /dev/null ; Only used for dongle mode decoderFallBack = false ; Use software AMBE decoder
; Below values are for using this as a local DMR dongle (no ASL needed) useMicrophone = false ; Use app as just a fancy dongle for DMR useVox = false ; If using dongle mode (useMicrophone), enable VOX voxDecay = 2 ; Hang time in seconds voxTrigger = 200 ; Value to trip PTT (0-32767)
; Information for xx_Bridge.py [AMBE_AUDIO] server = 127.0.0.1 ; IP address of xx_Bridge.py fromDMRPort = 31000 ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg) toDMRPort = 31003 ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg) ambeSize = 49 ; 72 bit is HB_Bridge AMBE, 49 bit is IPSC_Bridge AMBE minTxTimeMS = 2000 ; Minimum time in MS for hang delay gatewayDmrId = 1112721 ; ID to use when transmitting from Analog_Bridge repeaterID = 11127213 ; ID of source repeater txTg = 31676 ; TG to use for all frames received from Analog_Bridge -> xx_Bridge txTs = 2 ; Slot to use for frames received from Analog_Bridge -> xx_Bridge colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver ; This matches the rpt.conf ASL file with a setting like: ; rxchannel = usrp/127.0.0.1:34001:32001 [USRP] server = 127.0.0.1 ; IP address of Allstar/Asterisk toASLPort = 32001 ; PCM from ASL fromASLPort = 34001 ; PCM to ASL aslAudio = AUDIO_USE_AGC ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN) agcGain = -20 ; Gain (in db) of the AGC filter dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_GAIN, AUDIO_BPF) dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder ; Use top server and port if using AMBEServer ; Use bottom server/port and serial = true if using the DV3000u (thumbdv) [DV3000] ; server = 127.0.0.1 ; IP address of AMBEServer ; port = 2460 ; Port of AMBEServer server = /dev/ttyUSB0 ; Device of DV3000U on this machine port = 460800 ; Baud rate of the dongle serial = true ; Use serial (DV3000U) or IP
And my hblink.cfg:
# PROGRAM-WIDE PARAMETERS GO HERE # PATH - working path for files, leave it alone unless you NEED to change it # PING_TIME - the interval that clients will ping the master, and re-try registraion # - how often the Master maintenance loop runs # MAX_MISSED - how many pings are missed before we give up and re-register # - number of times the master maintenance loop runs before de-registering a client [GLOBAL] PATH: ./ PING_TIME: 5 MAX_MISSED: 3
# SYSTEM LOGGER CONFIGURAITON # This allows the logger to be configured without chaning the individual # python logger stuff. LOG_FILE should be a complete path/filename for *your* # system -- use /dev/null for non-file handlers. # LOG_HANDERLS may be any of the following, please, no spaces in the # list if you use several: # null # console # console-timed # file # file-timed # syslog # LOG_LEVEL may be any of the standard syslog logging levels, though # as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones # used. # [LOGGER] LOG_FILE: /var/log/hblink.log LOG_HANDLERS: console-timed LOG_LEVEL: DEBUG LOG_NAME: HBlink
# DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES # Ok, not the TGID, there's no master list I know of to download # This is intended as a facility for other applcations built on top of # HBlink to use, and will NOT be used in HBlink directly. # STALE_DAYS is the number of days since the last download before we # download again. Don't be an ass and change this to less than a few days. [ALIASES] TRY_DOWNLOAD: True PATH: ./ PEER_FILE: peer_ids.csv SUBSCRIBER_FILE: subscriber_ids.json TGID_FILE: talkgroup_ids.json PEER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?table=repe$ SUBSCRIBER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?tabl$ STALE_DAYS: 7
# EXPORT AMBE DATA # This is for exporting AMBE audio frames to an an "external" process for # decoding or other nefarious actions. [AMBE] EXPORT_IP: 127.0.0.1 EXPORT_PORT: 1234
# MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS # HomeBrew Protocol Master instances go here. # IP may be left blank if there's one interface on your system. # Port should be the port you want this master to listen on. It must be unique # and unused by anything else. # Repeat - if True, the master repeats traffic to clients, False, it does nothing. [MASTER-1] MODE: MASTER ENABLED: False REPEAT: True EXPORT_AMBE: False IP: PORT: 54000 PASSPHRASE: s3cr37w0rd GROUP_HANGTIME: 5
# CLIENT INSTANCES - DUPLICATE SECTION FOR MULTIPLE CLIENTS # There are a LOT of errors in the HB Protocol specifications on this one! # MOST of these items are just strings and will be properly dealt with by the program # The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz. # Latitude is an 8-digit unsigned floating point number. # Longitude is a 9-digit signed floating point number. # Height is in meters [REPEATER-1] MODE: CLIENT ENABLED: True EXPORT_AMBE: False IP: PORT: 54001 MASTER_IP: 3102.repeater.net MASTER_PORT: 62031 PASSPHRASE: passw0rd CALLSIGN: K4KSA RADIO_ID: 11127213 RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 3 LATITUDE: 27.863859 LONGITUDE: -82.833252 HEIGHT: 40 LOCATION: Seminole, Florida DESCRIPTION: DMR<> Allstar Gateway URL: https://groups.io/g/DVSwitch SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 OPTIONS:
Any help would be appreciated! Steve
|
|
Steve,
toggle quoted messageShow quoted text
Assumptions: You are running HB_Bridge.py not hblink.py HB_Bridge ports are pointing at Analog_Bridge ports. Post your HB_Bridge config file. Steve
On 04/14/2018 05:15 PM, Steve Siesel
[K4KSA] wrote:
|
|
Steve Siesel [K4KSA]
I am running hblink.py…… In the new install I did not have a HB_Bridge.py so I copied it from the old install and placed in the new one…..Still not working… restarted all services…
################################################ # HB_Bridge configuration file. ################################################
[DEFAULTS] gateway = 127.0.0.1 # IP address of Partner Application (IPSC_Bridge, Analog_Bridge) fromGatewayPort = 31003 # Port HB_Bridge is listening on for data (HB_Bridge <--- Partner) toGatewayPort = 31000 # Port Partner is listening on for data (HB_Bridge ---> Partner)
[RULES] # Name = Old TG, New TG, New Slot TG_SE = 3174, 3174, 2 TG_NA = 3,3,1 TG_ATL = 8,8,1 TG_WW = 1,1,1
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Saturday, April 14, 2018 5:57 PM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] ASL<>Analog_Bridge<>HBlink not working
Steve, On 04/14/2018 05:15 PM, Steve Siesel [K4KSA] wrote:
|
|
Pull everything from the HB_Bridge branch.
toggle quoted messageShow quoted text
On 04/14/2018 06:06 PM, Steve Siesel
[K4KSA] wrote:
|
|
Steve Siesel [K4KSA]
toggle quoted messageShow quoted text
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Saturday, April 14, 2018 6:08 PM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] ASL<>Analog_Bridge<>HBlink not working
Pull everything from the HB_Bridge branch. On 04/14/2018 06:06 PM, Steve Siesel [K4KSA] wrote:
|
|
-b HB_Bridge
sent via smoke signal (AT&T)
On Sat, Apr 14, 2018 at 6:10 PM -0400, "Steve Siesel [K4KSA]" <steve@...> wrote:
|
|