Date   

Re: Invalid command from BrandMeister #brandmeister

Veijo Arponen OH4VA
 
Edited

Well, I did a temporary solution and added this command in an else-if statement and pushed to the forked repository https://github.com/oh3nfc/HBlink/tree/devel

73 de Vepa


Re: More weird testing

Mike Zingman - N4IRR
 

I have been working on an update to Analog_Bridge to support IMBE as well as AMBE (72 and 49 bit versions).  A new data type was created to support the P25 audio stream.   I have also created some prototype code to support the P25 network.  This appears as a standard partner application just like IPSC_Bridge and HB_Bridge.  It will be called IMBE_Bridge.  The code is working well and I have had several QSOs on the P25 North American reflector in "dongle mode".  The code is rough, but is looking like we will have another possible digital parter before too long.

Mike


Re: More weird testing

Michael KD5DFB
 

Steve,

Can you share any details??

Michael KD5DFB

On Sun, Nov 19, 2017 at 9:57 PM, Steve N4IRS <szingman@...> wrote:
Just because,
We are ALPHA testing a software only P25 to analog bridge. For now it is connected to the North America MMDVM P25 reflector and outputting analog on AllStar node 2600 and Echolink N4IRS-L
It is receive ONLY. There is still a lot of work to do.

Steve N4IRS, Milke N4IRR

--
"What is IMBE_Bridge?"






Invalid command from BrandMeister #brandmeister

Veijo Arponen OH4VA
 

Hello all, this is my first message to this group.

I started using the HBlink last weekend. My conference bridge has two masters (Trunk and HBlink) and and one client (Brandmeister). The client is connected to the Finnish BrandMeister server 2441. The BM link works but every now and then in the log file comes error messages:

ERROR 2017-11-21 10:12:33,088 (Brandmeister) Received an invalid command in packet: 52505453424b4e0e8fbff7

Any idea what this is and how to solve it?

Cheers de Veijo OH3NFC


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Steve N4IRS
 

Matthew,
You are correct dmr_utils is not imported into hb_confbridge.py In your previous message you referenced HB_Bridge, where it is used.

73, Steve N4IRS

On 11/20/2017 04:23 AM, Matthew 2E0SIP wrote:

Hi Mike,

Unless I'm missing something, that function from dmr_utils isn't imported into hb_confbridge.py. It looks like it's only present in HB_Bridge.py.

Also as far as I can tell it only rewrites the rptr_id on packets going Master to Client, It doesn't rewrite it when going Client to Master.

Cheers

Matthew

2E0SIP


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Steve N4IRS
 

As Matthew said, Kurt OE1KBC has a closed source Hytera to MMDVM solution. It should work to bring a Hytera into a HB Network. I asked for information on the protocol and was told it is proprietary. There is some information on the net and I think some other systems are built on the same protocol. That all being said, without Hytera repeaters and time, reverse engineering the Hytera protocol is not going to happen anytime soon.

73, Steve N4IRS

On 11/20/2017 09:05 PM, Matthew 2E0SIP wrote:

Hi Bob,

There is some software written by OE1KBC to convert the Hytera protocol to the MMDVM protocol available here - http://ham-dmr.at/index.php/download/
I don't have access to a Hytera repeater so I've not tested it personally, but I understand it works well. 

Riku, I will let the other guys comment on the best practices to setup what you need.

Cheers
Matthew
2E0SIP



Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Bob kc2cwt
 

Thanks i will have a look , Wen i have a min .

I just pick up a 2 Hytrea repeater i will give it a try



On 11/20/2017 09:05 PM, Matthew 2E0SIP wrote:

Hi Bob,

There is some software written by OE1KBC to convert the Hytera protocol to the MMDVM protocol available here - http://ham-dmr.at/index.php/download/
I don't have access to a Hytera repeater so I've not tested it personally, but I understand it works well. 

Riku, I will let the other guys comment on the best practices to setup what you need.

Cheers
Matthew
2E0SIP


-- 
Bob KC2CWT
Carmel NewYork USA
(914)497-5502


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Matthew 2E0SIP
 

Hi Bob,

There is some software written by OE1KBC to convert the Hytera protocol to the MMDVM protocol available here - http://ham-dmr.at/index.php/download/
I don't have access to a Hytera repeater so I've not tested it personally, but I understand it works well. 

Riku, I will let the other guys comment on the best practices to setup what you need.

Cheers
Matthew
2E0SIP


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Bob kc2cwt
 

Would be nice to see Hytrea repeater in thair ..

KC2CWT
Bob Schneider
kc2cwt@...
(914)497-5502


-----Original Message-----
From: OH1E Riku <riku@...>
To: DVSwitch@groups.io
Sent: Mon, 20 Nov 2017 6:06 PM
Subject: Re: [DVSwitch] Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

heya, thanks for answers, it seems ppl understanding what is about.
is there any way to easily change the code to get this working?
the id of mmdvm and openspot (and connecting client of main hub) must be same to route any other place.. rptr_id i think is the issue
wanted also create multiple TG:s. for each tg need a separate master.. like a parrot is tg and main hub just route right tg for it.
creating mini dmr network what is self sustained in case other network its broken
de OH1E


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

OH1E Riku
 

heya, thanks for answers, it seems ppl understanding what is about.
is there any way to easily change the code to get this working?
the id of mmdvm and openspot (and connecting client of main hub) must be same to route any other place.. rptr_id i think is the issue
wanted also create multiple TG:s. for each tg need a separate master.. like a parrot is tg and main hub just route right tg for it.
creating mini dmr network what is self sustained in case other network its broken
de OH1E


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Matthew 2E0SIP
 

Hi Mike,

Unless I'm missing something, that function from dmr_utils isn't imported into hb_confbridge.py. It looks like it's only present in HB_Bridge.py.

Also as far as I can tell it only rewrites the rptr_id on packets going Master to Client, It doesn't rewrite it when going Client to Master.

Cheers

Matthew

2E0SIP


Re: Analog Bridge and DStar

Peter M0NWI
 

Mike,

Most of these DV tools need a,fair modicum of networking understanding, I think what Steve is proposing is that you use the tools in the Linux shell, netstat, ping and telnet to confirm the socket listeners are actually hosting the services you think they are from one box to the others.

73,
Peter M0NWI

Sent from Outlook
From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Mike Swiatkowski via Groups.Io <mjswiatk@...>
Sent: 20 November 2017 04:58:48
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Analog Bridge and DStar
 
If you mean setting localhost to the local repeater IP on the LAN and not 127.0.0.1 I did that.  BTW, when I load DummyRepeater it has a DEBUG suffix on it.  Is that right?

Could there be any dependency issues if it compiled?  I'm at a complete loss here. 

Mike


Re: Analog Bridge and DStar

Mike, AA9VI
 

If you mean setting localhost to the local repeater IP on the LAN and not 127.0.0.1 I did that.  BTW, when I load DummyRepeater it has a DEBUG suffix on it.  Is that right?

Could there be any dependency issues if it compiled?  I'm at a complete loss here. 

Mike


Re: Analog Bridge and DStar

Mike, AA9VI
 

How do I do that?


More weird testing

Steve N4IRS
 

Just because,
We are ALPHA testing a software only P25 to analog bridge. For now it is connected to the North America MMDVM P25 reflector and outputting analog on AllStar node 2600 and Echolink N4IRS-L
It is receive ONLY. There is still a lot of work to do.

Steve N4IRS, Milke N4IRR

--
"What is IMBE_Bridge?"


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Mike Zingman - N4IRR
 

HB_Bridge does rewrite the repeater id.  See dmr_utils/ambe_bridge.py lines 453-455


Re: Trying to setup a basic 'Parrot', however hb_confbridge.py is not matching the RADIO_ID

Matthew 2E0SIP
 

Hi Riku,

As it happens I've been using HB_Bridge today.

I've taken a look at the code, and HB_Bridge doesn't rewrite the RptrId, referred to as the radio_id in the code, but a 'master' will validate it on arrival to ensure its one of the connected clients.

So the following is currently impossible-


MMDVMHost --> ( HBLink Master | HBLink Client ) --> HBLink Master.

To make this work, its either necessary to re-write the RptrId as it passes through the intermediate instance of HBLink, or to not validate it on arrival at the master.

 


Re: Analog Bridge and DStar

Steve N4IRS
 

You may want to make sure ircDDBGateway is actually listening to the network not on the localhost IP.

On 11/19/2017 07:58 PM, Mike Swiatkowski via Groups.Io wrote:
Steve,
XRF and DCS don't seem to work on my end maybe due to a registration issue.  I'm going to have to table this for a while... It's consuming way too much time (like 3 or 4 days now) and I have to spend time with family. Something is seriously flawed with that Dummy Repeater install and the ability for it to talk to the gateway on the same LAN.  Thanks for your help.  We'll chat again later.

Mike, AA9VI


On Sunday, November 19, 2017, 9:49:20 AM CST, Steven Blackford <kb7sqi@...> wrote:


Hi Mike,
    Sorry for the delay in getting back to you.  You need to do 2 things before compile DummyRepeater & install it.  After you do your git pull, you need to make sure you copy the modified version of DummyRepeaterThread.cpp from the Analog_Bridge/DummyRepeater directory into the OpenDV/DummyRepeater/DummyRepeater/ Like so:

kb7sqi@kb7sqi-odroid:~$ cd tmp/source/g4klx/OpenDV/DummyRepeater/
kb7sqi@kb7sqi-odroid:~/tmp/source/g4klx/OpenDV/DummyRepeater$ cp ~/tmp/source/n4irs/Analog_Bridge/DummyRepeater/DummyRepeaterThread.cpp DummyRepeater/DummyRepeaterThread.cpp

You can make a backup of the original file first if you like.  You have to have the modified version from Steve, N4IRS's git hub for this all to work.  After you done that, then you need to configure DummyRepeater to include the ThumbDV/AmbeServer/Star*DV Support.  Here's how you do that:


./configure  --with-ambeserver --with-stardv

This will include support for both the ThumbDV/DV3000 & the Star*DV Dongle.  If you don't need the Star*DV Dongle, you can leave the --with-stardv off.  If you want to use this on a PI, then you need to make sure you include  ---with-gpio as well to support the PIDV Board.  Once configure has ran, then go ahead & do your make, install it, etc.

Make sure to read the Notes.txt file about this:

The modified version of DummyRepeater will use the USRP channel driver from AllS
tarLink (Just like Analog_Bridge)
DummyRepeater will use the default UDP ports for TX and RX. It uses address 127.
0.0.1 as defined by the USRP channel driver.
If you need to use other ports or addresses, you can define them in the enviorme
nt before you start dummyrepeter.

USRP_IP="127.0.0.1";export USRP_IP
USRP_TXPORT=34001;export USRP_TXPORT
USRP_RXPORT=32001;export USRP_RXPORT

Now when you start DummyRepeater, do it with the --verbose option:

$ dummyrepeater --verbose

That will give you more info in your Dummy_Repeater Log that'll be in the user home directory from where you start DummyRepeater.  When you start up DummyRepeater, it will complain if it can't connect to ircDDBGateway.  Check your ircDDBGateway logs also.  That should get you going in the right direction.  If you have any further questions, let me know.  

Steve, K4SQI



On Sun, Nov 19, 2017 at 12:54 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote:
Maybe a better question would be what are the proper steps for compiling Dummy Repeater?  I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater".  Do I need to compile with the AMBE tag?  Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for
libwxbase2.8-0_2.8.12.1+dfsg2- dmo4_amd64.deb
libwxgtk2.8-0_2.8.12.1+dfsg2- dmo4_amd64.deb

My ircddbgateway is at 10.1.1.31
My Dummy is at 10.1.1.2

I set repeater 2 in gateway as  Dummy and 10.1.1.2
I set Dummy gateway as 10.1.1.31...

I'm missing something...


cd ~
git clone https://github.com/dl5di/ OpenDV.git

cd ~/OpenDV
git pull

cd ~/OpenDV/DummyRepeater
./configure
make
sudo make install



--
-----
Steve, kb7sqi@...


Re: Analog Bridge and DStar

Mike, AA9VI
 

Steve,
XRF and DCS don't seem to work on my end maybe due to a registration issue.  I'm going to have to table this for a while... It's consuming way too much time (like 3 or 4 days now) and I have to spend time with family. Something is seriously flawed with that Dummy Repeater install and the ability for it to talk to the gateway on the same LAN.  Thanks for your help.  We'll chat again later.

Mike, AA9VI


On Sunday, November 19, 2017, 9:49:20 AM CST, Steven Blackford <kb7sqi@...> wrote:


Hi Mike,
    Sorry for the delay in getting back to you.  You need to do 2 things before compile DummyRepeater & install it.  After you do your git pull, you need to make sure you copy the modified version of DummyRepeaterThread.cpp from the Analog_Bridge/DummyRepeater directory into the OpenDV/DummyRepeater/DummyRepeater/ Like so:

kb7sqi@kb7sqi-odroid:~$ cd tmp/source/g4klx/OpenDV/DummyRepeater/
kb7sqi@kb7sqi-odroid:~/tmp/source/g4klx/OpenDV/DummyRepeater$ cp ~/tmp/source/n4irs/Analog_Bridge/DummyRepeater/DummyRepeaterThread.cpp DummyRepeater/DummyRepeaterThread.cpp

You can make a backup of the original file first if you like.  You have to have the modified version from Steve, N4IRS's git hub for this all to work.  After you done that, then you need to configure DummyRepeater to include the ThumbDV/AmbeServer/Star*DV Support.  Here's how you do that:


./configure  --with-ambeserver --with-stardv

This will include support for both the ThumbDV/DV3000 & the Star*DV Dongle.  If you don't need the Star*DV Dongle, you can leave the --with-stardv off.  If you want to use this on a PI, then you need to make sure you include  ---with-gpio as well to support the PIDV Board.  Once configure has ran, then go ahead & do your make, install it, etc.

Make sure to read the Notes.txt file about this:

The modified version of DummyRepeater will use the USRP channel driver from AllS
tarLink (Just like Analog_Bridge)
DummyRepeater will use the default UDP ports for TX and RX. It uses address 127.
0.0.1 as defined by the USRP channel driver.
If you need to use other ports or addresses, you can define them in the enviorme
nt before you start dummyrepeter.

USRP_IP="127.0.0.1";export USRP_IP
USRP_TXPORT=34001;export USRP_TXPORT
USRP_RXPORT=32001;export USRP_RXPORT

Now when you start DummyRepeater, do it with the --verbose option:

$ dummyrepeater --verbose

That will give you more info in your Dummy_Repeater Log that'll be in the user home directory from where you start DummyRepeater.  When you start up DummyRepeater, it will complain if it can't connect to ircDDBGateway.  Check your ircDDBGateway logs also.  That should get you going in the right direction.  If you have any further questions, let me know.  

Steve, K4SQI



On Sun, Nov 19, 2017 at 12:54 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote:
Maybe a better question would be what are the proper steps for compiling Dummy Repeater?  I'm assuming ithey steps are at the bottom of this message that I copied and to launch with the command "dummyrepeater".  Do I need to compile with the AMBE tag?  Are there any special tricks with DummyRepeater and Jessie other than downloading the .deb and installing manually for
libwxbase2.8-0_2.8.12.1+dfsg2- dmo4_amd64.deb
libwxgtk2.8-0_2.8.12.1+dfsg2- dmo4_amd64.deb

My ircddbgateway is at 10.1.1.31
My Dummy is at 10.1.1.2

I set repeater 2 in gateway as  Dummy and 10.1.1.2
I set Dummy gateway as 10.1.1.31...

I'm missing something...


cd ~
git clone https://github.com/dl5di/ OpenDV.git

cd ~/OpenDV
git pull

cd ~/OpenDV/DummyRepeater
./configure
make
sudo make install




--
-----
Steve, kb7sqi@...


Re: Analog Bridge and DStar

Steven Blackford
 

Mike,
   You could also copy my file into place.  Startup Dummy Repeater & edit the configuration to match your setup, change the call signs from K4SQI to yours, etc.  Make sure the RPT 1 & RPT 2 settings are correct as well.  You'll see mine is "K4SQI  A" & "K4SQI  G"  Those are important to make sure you have the proper spacing etc.  Make sure your ircDDBGateway config is also setup properly so it can communicate with Dummy Repeater.  Let me know how it goes.  If you need to, you can reach me on BM TG 31254.  I always monitor that via D-Star/DMR/C4FM.  

Steve, K4SQI

On Sun, Nov 19, 2017 at 11:55 AM, mjswiatk via Groups.Io <mjswiatk@...> wrote:
I did what you said and here is the error log from Dummy Repeater.  What does this mean?  The 48000 rate seems odd.  Why isn't it 460800?  Still, the GUI is visually up but it really doesn't see any traffic or seem to do anything.

Mike

: 2017-11-19 00:05:43: DV3000 chip identified as: AMBE3000R
M: 2017-11-19 00:05:43: Opened hw:0,0 hw:0,0 Rate 48000
M: 2017-11-19 00:05:43: Starting ALSA reader thread
M: 2017-11-19 00:05:43: Starting ALSA writer thread
E: 2017-11-19 00:06:44: Error returned from sendto, err=22
E: 2017-11-19 00:07:44: Error returned from sendto, err=22
E: 2017-11-19 00:08:44: Error returned from sendto, err=22
M: 2017-11-19 00:09:23: DV3000 chip identified as: AMBE3000R
M: 2017-11-19 00:09:23: Opened hw:0,0 hw:0,0 Rate 48000
M: 2017-11-19 00:09:23: Starting ALSA reader thread
M: 2017-11-19 00:09:23: Starting ALSA writer thread
M: 2017-11-19 00:10:19: DV3000 chip identified as: AMBE3000R
M: 2017-11-19 00:10:19: Opened hw:0,0 hw:0,0 Rate 48000
M: 2017-11-19 00:10:19: Starting ALSA reader thread
M: 2017-11-19 00:10:19: Starting ALSA writer thread
M: 2017-11-19 00:10:24: Transmitting to - My: WX9NC   /B     Your: CQCQCQ    Rpt1: WX9NC  G  Rpt2: WX$
E: 2017-11-19 00:10:24: Error returned from sendto, err=22
E: 2017-11-19 00:10:24: Error returned from sendto, err=22
E: 2017-11-19 00:10:24: Error returned from sendto, err=22




--
-----
Steve, kb7sqi@...

10121 - 10140 of 10634