April 2017 - Allstar-Digital - lists.keekles.org

hb_ambe_audio
by Steve Zingman 25 Apr '17

25 Apr '17

Mike and I are beta testing ambe_audio and DMRGateway for HBlink. So far so good. The issues with fluttering analog signals and fast keyups has been addressed. This should resolve the issue of the outbound DMR signal lagging behind the analog signal more then a short normal display. This is BETA testing. It is not ready to be released. I am connecting to a number of high activity ASL hubs to test operation. Right one I have it in receive ONLY so we have one way ASL ---> DMR. I am testing on BM The DMR ID is 1311222 and the TG 311222. The ASL node connected is 2135. Let's see how this goes. One advantage to hb_audio is that there is no longer a need to involve BM sysadmins to setup static routing for your connection to BM. hb_ambe_audio also supports smaller local networks of MMDVM based devices without the need for a BM server or a c-Bridge. hb_ambe_audio and hb_parrot provides us insight into connecting other devices to a HBlink network. for DVSwitch, 73 Steve N4IRS -- --- "Real programmers use vi, that's why I use nano."

6 13

DMRGateway failure
by Robert Newberry 20 Apr '17

20 Apr '17

I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem. Here is the problem. -When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR. This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally. I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of. Does anyone have any suggestions on how I should start troubleshooting this? -- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com

6 32

DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u /PiDV /HBlink
by Steve Zingman 19 Apr '17

19 Apr '17

Can I fit anything else on the subject line? Mike has identified a bug in how the transition from transmit to receive is signaled between chan_usrp and DMRGateway. This effects fast short ASL ---> DMR transmissions and weak ASL signals. In preparation for rethinking the signaling from chan_usrp to DMRGateway, there is some other work to be done. Some of this work not only affects DMRGateway. DMRGateway will need some re-work. The upside to the work needed is that a couple of new modules will be created for HBlink. The first is hb_parrot. hb_parrot.py is in the HBlink repository now. The second is ... hb_ambe_audio. What this amounts to is DMRGateway will be able to use either DMRlink or HBlink to connect to their respective networks. DMRGateway will support both IPSC based networks (DMR-MARC, DCI etc) and Home Brew Protocol supporting networks (BM) The big plus to DMRGateway running with HBlink is that it will NOT require any interaction with the BM sysops! And, maybe a few other goodies and refinements. along the way. For DVSwitch, 73, Steve N4IRS

2 1

DMRGateway testing
by ve2dje＠gmail.com 14 Apr '17

14 Apr '17

Hi to everyone . My DMR Gateway software suite is installed and all the testing in the procedure are OK.. I am connecting to Brandmeister 3108 port 55001 TG 3027 . All response are OK . The Brandmeister site shows my DMRlink on the Last Heard window as a Smart PTT Bridge My DMRGAteway windows shows the connection to 127.0.0.1 port 31000 and to my AST USRP 34001 When I do PTT and test audio from Iaxrpt connected to my node . The RED and Green leds on th Thumbsb are flashing. LH list on the server is updated . My DMRGatewy windows shows “Connected ( PTT asserted)” and “Disconnected ( PTT off)” when released My ambe_audio windows shows `” INFO Transmit from gateway to TG3027:” then “INFO Transmit complete “ on PTT release My test MMDVM repeater opened on TG 3027 receives a PTT from network. BUT No audio ( only faint high frequency buzz ) No activity on Hoseline even if Last Heard is being updated..... Any hints as how to test the ThumbDV output ??? Have been experimenting with the outputAudioDevice in DMRGateway.ini without success..... Deffective ThumbDV ?????? . How can I make shure ???? Also I am hearing some audio out on AST node that is not coming from TG3027 ?????? My entry in ambe_audio.cfg is TGfilter = 3027,4327 Loaded the system twice from scratch and ..... Same..... Thanks for any advice Richard VE2DJE Provenance : Courrier pour Windows 10

5 7

DMRGateway /DMRGui question
by Guy Vachon VE2VAG 10 Apr '17

10 Apr '17

Hello Steve and the group, I want to try using DMRGateway in dongle mode. I’ve browsed thru all the mailing list topics to recuperate all the needed infos, and will try to set it up next weekend on a spare Raspberry PI 2. I also have a ThumbDV AMBE dongle. I’ve checked your “Digital Voice Switch” website, and in the files section, the link for the DMRGui app to control DMRGateway does not work. Is it still available to test and try ? I’ll surely have other questions along the way, but I think I should have almost everything I need to experiment for now. I mainly want to connect to Brandmeister, and try the french canadian talkgroup. Thanks and 73s from Guy VE2VAG Quebec, Canada

5 27

3101 issue
by Robert Newberry 10 Apr '17

10 Apr '17

Has anyone been noticing issues on 3101? At one point yesterday it wasnt even listed on the master list on Brandmeister.network. On the ride home it wasn't working. By not working I mean I will put my call out on BM TG 3167 and listen for it on my Allstar repeaters. I only ask because last week I had an issue but it was related to my configuration on the BM server side. I'm just trying to figure out why my connection has been so intermittent. Things started acting funny starting Sunday afternoon that I am aware of. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com

3 4

Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u/PiDV
by Guy Vachon VE2VAG 07 Apr '17

07 Apr '17

Hello Steve, Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results With the -n switch, the dongle never sends back the >0AMBE3000R >Version >6100010031 >Wrote: 5 bytes >a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment. When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400. Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch. Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that. BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days. On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything. Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know. 73's from Guy VE2VAG _______________________________________________ Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman(a)msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital(a)lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9(a)msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests. Steve On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote: > Richard, > I was having the same problem as you, since I own a first generation > ThumbDV which runs at 230400 bauds. > When I removed the –n argument in the command: *python AMBEtest3.py -n > -s /dev/ttyUSB0, *it then worked for me. > So for people with first generation ThumbDV’s, the command *python > AMBEtest3.py -s /dev/ttyUSB0 *must be used. > Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini > UNLESS your DV is not at /dev/ttyUSB0 > If you run a first gen ThumbDV, the baud rate must be changed in it > also to 230400. > And for Steve: thank you very much for all the efforts in the software > and the documents. I went thru it all, and except for the items > mentionned up here, everything went well and I’m ready for the next steps. > Thanks and 73s from Guy VE2VAG > > > _______________________________________________ > Allstar-Digital mailing list > Allstar-Digital(a)lists.keekles.org > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital

4 7

Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u/PiDV
by ve2vag 07 Apr '17

07 Apr '17

Thanks very much Steve ! I'll play with all of this, and update dmrlink during the week end. Will keep posted on how it goes Envoyé depuis mon téléphone intelligent Samsung Galaxy. -------- Message d'origine --------De : Steve Zingman <szingman(a)msgstor.com> Date : 17-04-07 06:08 (GMT-05:00) À : Digital linking using Asterisk and app_rpt <allstar-digital(a)lists.keekles.org> Objet : Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u/PiDV Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg. As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip> 73, Steve N4IRS On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote: > Hello Steve, > > Sorry for the delay in answering, was overloaded with work. > Dunno if you still needed the test, but anyhow, I've tried again the > command with and without the -n switch, and also 2 times back to back > with the -n switch (if I understood correctly the test you asked for) > and still the same results > > With the -n switch, the dongle never sends back the >> 0AMBE3000R >> Version >> 6100010031 >> Wrote: 5 bytes >> a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 > we are expecting. When the –n switch is removed from the the command, > I do receive it at the moment. > > When I was making tests, I’ve checked the dongle’s serial baud rate > with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was > at 460800 bauds. > I bought my ThumbDV when they came out at first, way before the new > model that is at 460800, so I knew mine was at 230400. > > Even if i tried sending the command python “AMBEtest3.py -n -s > /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 > with "stty -F /dev/ttyUSB0 230400", it would not work. > Only way to ge the expected result was by removing the –n switch. > > Also, the AMBEtest3.py python command with the –n switch removed > always worked, even without trying setting the baud rate of the > dongle at 230400 before that. > > BTW, I'm using the RC1 image from the links in your instructions. And > the above tests were made without doing any git pull that I was in the > posts made during the last couple of days. > > On my side, I went thru all the instructions from your document, and > I'm ready for the next part about the configuration. But I know you, > Mike and the rest of the team are working hard with bug hunting, so > please keep up the good work and thanks for everything. > > Also, in regard of my initial question about DMRGui, it was because > the link for it in the files section of the DVhamswitch website sends > us on a parked domain for sale at vyous.com, so that link is dead. > Just in case you didn't know. > > 73's from Guy VE2VAG > _______________________________________________ > > Date: Wed, 5 Apr 2017 08:14:57 -0400 > From: Steve Zingman <szingman(a)msgstor.com> > To: Digital linking using Asterisk and app_rpt > <allstar-digital(a)lists.keekles.org> > Subject: Re: [Allstar Digital] DMRGateway / DMRGui / > DMRLink/ambe_audio / DV3000u/PiDV > Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9(a)msgstor.com> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Guy, > I do not have the first generation ThumbDV. Could you try with the -n > switch and when it fails, try with the -n switch? No reboot between > tests. > > Steve > > On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote: >> Richard, >> I was having the same problem as you, since I own a first generation >> ThumbDV which runs at 230400 bauds. >> When I removed the –n argument in the command: *python AMBEtest3.py -n >> -s /dev/ttyUSB0, *it then worked for me. >> So for people with first generation ThumbDV’s, the command *python >> AMBEtest3.py -s /dev/ttyUSB0 *must be used. >> Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini >> UNLESS your DV is not at /dev/ttyUSB0 >> If you run a first gen ThumbDV, the baud rate must be changed in it >> also to 230400. >> And for Steve: thank you very much for all the efforts in the software >> and the documents. I went thru it all, and except for the items >> mentionned up here, everything went well and I’m ready for the next >> steps. >> Thanks and 73s from Guy VE2VAG >> >> >> _______________________________________________ >> Allstar-Digital mailing list >> Allstar-Digital(a)lists.keekles.org >> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > >

1 0

DMRgui
by Robert Newberry 07 Apr '17

07 Apr '17

I'd like to play with DMRgui. I only have a Unbuntu laptop. It looks like it runs on python so I could run it on mu Ubuntu box? Next question is, can I connect this to my existing IPSC network as a peer? It looks like I need to point it to where my RPI/DV3000 resides. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com

1 0

Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u/PiDV
by Guy Vachon VE2VAG 05 Apr '17

05 Apr '17

Richard, I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me. So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used. Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400. And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps. Thanks and 73s from Guy VE2VAG

3 3