DM3MATJust released #qdmr 0.14.0. This feature release adds AM (air band) channels and support for the Baofeng DM-32UV. Happy testing!
Ekki DF4ORYou mention under "install", that #qdmr is in the Arch repo. It isn't, it's only available through AUR.
Adrian@dm3mat
Really nice software! I wish I could use it to program my radios instead of having to spin up a VM for that.
Alas, Hytera doesn't even have an in-tree USB driver. If you ever find out some info about Hytera USB on Linux, I'd greatly appreciate if you can post it.
Really nice software! I wish I could use it to program my radios instead of having to spin up a VM for that.
Alas, Hytera doesn't even have an in-tree USB driver. If you ever find out some info about Hytera USB on Linux, I'd greatly appreciate if you can post it.
tarxvf@tarxvf @dm3mat
Found a patch for Hytera rndis_host that seems to have been commited by @gregkh a while ago: https://lore.kernel.org/all/2022010117[email protected]/
My H-series radios are not detected though with kernel 6.12
@tarxvf
lsusb -v
```
Bus 003 Device 032: ID 238b:0a11 Hytera Communications DMR Radio
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x238b Hytera
```
@yo8rzz I love how Hytera isn't even consistent among their own radios.
I don't have any of those models so I'm not any help here!
I don't have any of those models so I'm not any help here!
@yo8rzz Interfaceing the Hytera devices is not the issue. You can talk to all USB devices via libusb. It is the firmware. Hytera actively tries to prevent any other software to write codeplugs. If you flip any bit, it bricks the device. And you need to patch the original CPS to revive it. On my side, it is not worth the hustle.