[chirp_users] TYT DMR Radios
blueneon at gmail.com
Mon Jan 1 18:52:54 PST 2018
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
On Jan 1, 2018 5:48 PM, "David Ranch" <chirp at trinnet.net> wrote:
Per http://www.linux-usb.org/usb.ids , this seems like 0483:df11 is:
df11 STM Device in DFU Mode
That's NOT a serial port.
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:
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:
Jan 1 18:55:42 kp4djt-t420 mtp-probe: checking bus 1, device 9:
Jan 1 18:55:42 kp4djt-t420 mtp-probe: bus: 1, device: 9 was not an MTP
The DMRTOOLS talk to it just fine, now to figure out how to get it to talk
radio from wine. Also the device does not appear in /dev unlike serial
On Mon, Jan 1, 2018 at 1:08 PM, Nigel Johnson <nw.johnson at ieee.org> wrote:
> If you are having trouble getting USB serial working in wine under linux,
> try this post:
> 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
> 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
> 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
> than just a bit trivial to add the DMR stuff, but maybe someone will
> 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> 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] On Behalf Of Neil
>> Sent: Monday, January 1, 2018 2:00 AM
>> To: 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)
chirp_users mailing list
chirp_users at intrepid.danplanet.com
This message was sent to Tom KG4CYX at blueneon at gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users