[Allstar Digital] DMR to AllStar

[David KE6UPI]

Thanks Mike that does help.. Back to the other email.. So when we use the
DV4Mini software we go out talkgroup 4639 and 4639 is not listed
in _tg_filter = 2,3,13,3174,3777215,3100,9,9998,3112.

Anyways thanks, David

On Wed, Dec 9, 2015 at 10:02 AM, Steve Zingman <szingman at msgstor.com> wrote:

> David,
> See if this helps.
> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.pdf>
> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.pdf>
>
> On 12/9/2015 11:44 AM, David KE6UPI wrote:
>
> Thanks Mike for the reply.
>
> My setup right now is DV4Mini and the Control Panel on my PC. But I really
> want to understand and help with the Allstar to DMR if I can.. I'm not a
> programmer and I'm very new to DMR. So the best I can do would be that guy
> to help test maybe. I can open my firewall to one of my RPi 2 on a 2nd
> network here at home so you could connect and play on the RPi 2.
>
> How are you connecting DMR to apt_rpt. Are you using chan_usrp? If so can
> you share your setup?
>
> Thanks again Mike
>
> David
>
> On Wed, Dec 9, 2015 at 8:10 AM, Mike Zingman <mike.zingman at gmail.com>
> wrote:
>
>> David,
>>
>> The ambe_audio.py is using a list of Talk Groups (TG).  When ever any of
>> the TGs in the list are encountered, the AMBE will be decoded and passed to
>> Allstar.  The current list of TGs is defined in ambe_audio.cfg:
>>
>> _tg_filter = 2,3,13,3174,3777215,3100,9,9998,3112
>>
>> So, node 2100 is looking for all of the above and will re-transmit them
>> on Allstar.  Looking deeper, we see TG9, but what reflector?  We are
>> currently pointing our TG9 routes to reflector 4639 as you can see here:
>>
>> http://174.36.222.36/
>>
>> Now, with that said, I did notice last night that when I was playing on
>> TG9/4639 and I was not seeing myself on the log output of DMRLink.  Steve
>> may have turned that off for a moment or there was a connectivity problem,
>> but you should be able to use your DV4Mini with standard control panel and
>> transmit on 4639 and hear yourself on 2100.
>>
>> Mike
>>
>>
>>
>> On Wed, Dec 9, 2015 at 7:40 AM, David KE6UPI < <dshaw at ke6upi.com>
>> dshaw at ke6upi.com> wrote:
>>
>>> Hello Mike, I have some questions about the DV4Mini I hope you could
>>> answer for me. When I have it setup I going seem to get the Talkgroup 9.
>>> I'm using a MD380 radio and would like to get on North America so I can
>>> hear myself on the Allstar node 2100. I have North America programmed on my
>>> radio.
>>>
>>> Any help would be great.
>>>
>>> David
>>> KE6UPI
>>>
>>> On Sun, Dec 6, 2015 at 11:12 AM, Mike Zingman < <mike.zingman at gmail.com>
>>> mike.zingman at gmail.com> wrote:
>>>
>>>> So we have a different thread for this device..
>>>>
>>>> From my perspective the dv4m is an interesting widget.  The hardware is
>>>> not special (it has been done before) but it is solid and inexpensive.  It
>>>> offers a fully digital interface to DMR from the RF side.  With the
>>>> published interface (see
>>>> http://dv4m.ham-dmr.ch/Dokumentation/TechnicalDocs/dv4mini_interface.pdf)
>>>> you can fully control the radio.
>>>>
>>>> The challenge is to use the raw I/O commands and build up an OPEN
>>>> system that will let us experiment.  Towards that end I have started a
>>>> framework that lets me communicate with the dongle.  This was fairly easy
>>>> and is currently sending and receiving DMR frames from my host software.
>>>>
>>>> I have also added code to the host to send and receive point to point
>>>> packets of DMR frames and will be testing this soon.  I have more work to
>>>> do here to finish the frame decoder, which will be used to better
>>>> synchronize the two peers.
>>>>
>>>> As you might expect, I have several different projects all in the
>>>> works, so multitasking this at the moment.  My eventual goal is to have a
>>>> generic framework that I can then use to connect any source with any sinc
>>>> (read local DMR subscriber radio with the world).
>>>>
>>>> So, why reinvent the wheel?  The dv4m already connects with the DMRPlus
>>>> and other networks.  What more could a ham want?  The easy answer: to
>>>> experiment.  The current code is not *open* and can not be used as the
>>>> basis for other projects.  In order to make this happen, open source is
>>>> required.  All of the code I am working on for the dv4m will be published
>>>> so others can build upon it.
>>>>
>>>>
>>>> Mike
>>>>
>>>>
>>>> _______________________________________________
>>>> Allstar-Digital mailing list
>>>> Allstar-Digital at lists.keekles.org
>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Allstar-Digital mailing list
>>> Allstar-Digital at lists.keekles.org
>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>
>>>
>>
>> _______________________________________________
>> Allstar-Digital mailing list
>> Allstar-Digital at lists.keekles.org
>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>
>>
>
>
> _______________________________________________
> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
>
> _______________________________________________
> Allstar-Digital mailing list
> Allstar-Digital at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20151209/61859e1c/attachment.html>