search

hmatuschek / qdmr

A GUI application for configuring and programming cheap DMR radios under Linux and MacOS X.
https://dm3mat.darc.de/qdmr/
GNU General Public License v3.0
223 stars 46 forks source link

MacOS 13.5 and AnyTone D878UV2Plus, cannot read/write to radio #369

Closed c-beezy closed 1 year ago

c-beezy commented 1 year ago

Hey all, I've got the following condition I cant get past:

When I fire up qdmr, I can successfully detect my radio with the detect function, with the following messages in the console:

Debug in lib/radio.cc@56: Try to detect radio at Serial interface 'cu.usbmodem0000000100001'.
Debug in lib/usbserial.cc@90: Try to open Serial interface 'cu.usbmodem0000000100001'.
Debug in lib/usbserial.cc@124: Opened serial port cu.usbmodem0000000100001 with 115200baud.
Debug in lib/anytone_interface.cc@307: Anytone: In program-mode now.
Debug in lib/anytone_interface.cc@336: Found radio 'D878UV2', version 'V100'.

But as soon as I close the modal UI box that says "Found device 'Anytone AT-D878UVII' ", I see this in the console:

Debug in lib/anytone_interface.cc@356: Anytone: Left program-mode.
Debug in lib/usbserial.cc@155: Serial port will close now.

And then the radio reboots.

When I try to read the codeplug from the radio, I get "no matching device was found" error in the UI, and the following output in the console:

Debug in lib/usbdevice.cc@247: Check if serial port cu.usbmodem0000000100001 still exisist and has VID:PID 28e9:18a.
Debug in lib/usbdevice.cc@251: Serial port (cu.usbmodem0000000100001) is not valid anymore.
Debug in src/application.cc@446: Last device is invalid, search for new one.
Debug in lib/usbserial.cc@162: Search for serial port with matching VID:PID 28e9:18a.
Debug in lib/usbserial.cc@162: Search for serial port with matching VID:PID 1fc9:94.
Debug in lib/dfu_libusb.cc@156: Search for DFU devices matching VID:PID 483:df11.
ERROR in src/application.cc@450: No matching devices found.

This is: an apple silicon mac running MacOS 13.5 qdmr v0.11.2 Firmware 3.02N on the radio.

Any idea whats going on here?

hmatuschek commented 1 year ago

The device appears not to be listed again by the OS. You do not need to detect the device before reading or writing to it. So, just connect it to the computer and hit read/write. However, once the device rebooted (takes some time), it should be accessible again.

c-beezy commented 1 year ago

Hey thanks a lot, I feel pretty dumb now. I assumed I needed to detect before trying to read it. It worked great, just like you said!