[chirp_users] TYT DMR Radios
David Ranch
Fri Jun 8 13:46:02 PDT 2018
Btw, just to chime into this thread, I just became aware of this DMR
radio programming tool. It seems somewhat like Chirp (except it's
Windows only) in the fact that it can program various different DMR radios:
http://n0gsg.com/contact-manager/
--
/DMR Contact Manager/ is a custom-designed software package designed for
use with Connect Systems CS700/CS701/CS750/CS800/CS801/CS800D radios, as
well as the Tytera MD-380/390/390GPS, TYT MD2017/MD9600, AnyTone
AT-D868UV and AT-D858, Retevis RT3, and similar radios that use the
RDT/RDB file formats. These units are MOTOTRBO-compatible DMR mobile
radios suitable for both commercial and amateur radio applications.
. . .
Contact Manager features direct connectivity to the Ham-Digital online
database. Worldwide call and user information is instantly available,
and directly importable into any codeplug. No more manual retyping of
contact information - - and for clubs supporting this radio,
incorporation of users into standardized codeplugs is now simple and
automated. Simply have your users register with Ham-Digital and let
Contact Manager update your organization's official codeplug. It's that
easy!
--
--David
KI6ZHD
On 01/04/2018 04:20 PM, Chuck Hast wrote:
> For those of you wanting an alternative to the TYT software, I have been
> testing Dale's work out, it does very very well. Yesterday i found my
> self with
> an improperly programmed DMR channel, I opened up my laptop (linux) and
> fired up editcp, went in and changed the TX frequency for the system
> in questiion
> and that was it. I can read and write code plugs from the radio quite
> fast, seems
> to be faster than the TYT software, also you can in the software drag
> and drop
> channels zones etc to different parts, or you can open to sessions and
> use drag
> and drop to build a new code plug.
>
> Again here is the URL:
> https://www.farnsworth.org/dale/codeplug/editcp/
> <https://www.farnsworth.org/dale/codeplug/editcp/>
>
> Now I have a nice accompaniment to Chirp that handles the DMR radio.
>
> One thing, it will show a lot of errors, these are actually in the
> code plug, just
> ignore them and press on.
>
> There is a version also for Windows, for those that want that solution.
>
> On Mon, Jan 1, 2018 at 8:57 PM, Tom Morris <blueneon at gmail.com
> <mailto:blueneon at gmail.com>> wrote:
>
> I saw someone mention working with the..... wonderful.... TYT
> software in this thread. Before you growl at it any more, check
> this out
>
> http://www.miklor.com/MD380/380-CPEditor.php
> <http://www.miklor.com/MD380/380-CPEditor.php>
>
> Works 100% in WINE. Only issue I've ever had with it is that some
> elements of the interface seem to get mouseover and click confused
> (you'll see what I mean after a moment if it affects your setup,
> no functionality is impaired by this however)
>
> I use this to edit the codeplug and send it onto the radio with
> the md380-tools utility
>
> On Jan 1, 2018 6:52 PM, "Tom Morris" <blueneon at gmail.com
> <mailto:blueneon at gmail.com>> wrote:
>
> The TYT cable is just a straight through cable.
>
> CHIRP would need a lot of functionality added to support dmr.
> First, the radio is like a "model 3" Motorola in that you need
> a zone/channel assignment. You'd need to implement this to use
> analog only.
> Then, to do dmr, you need timeslot, color code, and contacts.
> For each channel it will need an individual or group contact
> set, as well as an optional RX group list. You'll need to have
> the ability to edit the contacts and group lists.
>
> Not by any means saying it's impossible but it would be a big
> chunk of architecture to add to a package that only implements
> analog for the time being.
>
> On Jan 1, 2018 5:48 PM, "David Ranch" <chirp at trinnet.net
> <mailto:chirp at trinnet.net>> wrote:
>
>
> Per http://www.linux-usb.org/usb.ids
> <http://www.linux-usb.org/usb.ids> , this seems like
> 0483:df11 is:
>
> 0483 STMicroelectronics
> df11 STM Device in DFU Mode
>
>
> That's NOT a serial port.
>
> --David
> KI6ZHD
>
>
> On 01/01/2018 04:59 PM, Chuck Hast wrote:
>> The TYT dongle is not a serial device, here is the syslog
>> dump I get when I
>> plug the TYT dongle with radio connected.
>>
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.369938] usb
>> 1-1.1: new full-speed USB device number 9 using ehci-pci
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.469746] usb
>> 1-1.1: New USB device found, idVendor=0483, idProduct=df11
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.469756] usb
>> 1-1.1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.469762] usb
>> 1-1.1: Product: Patched MD380
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.469767] usb
>> 1-1.1: Manufacturer: @00000008 : ffffffff
>> Jan 1 18:55:42 kp4djt-t420 kernel: [ 535.469771] usb
>> 1-1.1: SerialNumber: 00000000010C
>> Jan 1 18:55:42 kp4djt-t420 mtp-probe: checking bus 1,
>> device 9:
>> "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1"
>> Jan 1 18:55:42 kp4djt-t420 mtp-probe: bus: 1, device: 9
>> was not an MTP device
>>
>> The DMRTOOLS talk to it just fine, now to figure out how
>> to get it to talk to the
>> radio from wine. Also the device does not appear in /dev
>> unlike serial devices.
>>
>>
>>
>> On Mon, Jan 1, 2018 at 1:08 PM, Nigel Johnson
>> <nw.johnson at ieee.org <mailto:nw.johnson at ieee.org>> wrote:
>>
>> If you are having trouble getting USB serial working
>> in wine under linux, try this post:
>>
>> https://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-your-serial-ports/
>> <https://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-your-serial-ports/>
>>
>> I do a lot of micro controller programming and
>> debugging using serial interfaces and I have used it
>> to get several different things working
>>
>> 73 de NIgel ve3id
>>
>>
>>
>> On 01/01/18 13:39, Chuck Hast wrote:
>>> Yes, we all use DMRTools on the MD-380 and similar,
>>> but still have to fall back
>>> on the stinking TYT software to actually generate
>>> the code plug, sure would
>>> like to be able to use one piece of software to do
>>> it. The TYT software runs
>>> under wine but it cannot see the dongle as wine does
>>> not appear to be able
>>> to handle USB devices so you have to make it a two
>>> step process as far as I
>>> can see.
>>>
>>> Yes we will need to find someone who can take on the
>>> Chirp work, as it is more
>>> than just a bit trivial to add the DMR stuff, but
>>> maybe someone will emerge.
>>> There are a lot of MD-380 people out there who would
>>> like to be able to use
>>> Chirp for the radio maybe one is a coder and will
>>> step forward.
>>>
>>>
>>>
>>> On Mon, Jan 1, 2018 at 11:57 AM, Silverfox
>>> <alan.r.hill at gmail.com
>>> <mailto:alan.r.hill at gmail.com>> wrote:
>>>
>>> Why do you need it. There is already excellent
>>> freeware software that
>>> allows you to program them.
>>> Happy New Year. 73's
>>> Alan - W6ARH
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: chirp_users-bounces at intrepid.danplanet.com
>>> <mailto:chirp_users-bounces at intrepid.danplanet.com>
>>> [mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <mailto:chirp_users-bounces at intrepid.danplanet.com>]
>>> On Behalf Of Neil Stone
>>> Sent: Monday, January 1, 2018 2:00 AM
>>> To: chirp_users at intrepid.danplanet.com
>>> <mailto:chirp_users at intrepid.danplanet.com>
>>> Subject: [chirp_users] TYT DMR Radios
>>>
>>> Good morning and happy new year all,
>>>
>>> I was wondering if there were any plans to add
>>> functionality to chirp to
>>> support the TYT DMR radios, such as their
>>> MD-2017 (...so last year) or
>>> MD-380 for example?
>>>
>>> That's all for now, 73
>>>
>>> Neil (M6LPI)
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180608/3a18e186/attachment.html
More information about the chirp_users
mailing list