New Model #10217
openRadioddity MU-5
0%
Description
It doesn't appear that the Radioddity MU-5 radio is support in CHIRP. Is there a supported Radioddity radio option to use instead? If not, could you please accept this as a request for support for this radio?
Files
Updated by Jim Unroe almost 2 years ago
Eric Swenson wrote:
It doesn't appear that the Radioddity MU-5 radio is support in CHIRP. Is there a supported Radioddity radio option to use instead? If not, could you please accept this as a request for support for this radio?
The MU-5 (MURS 5 channel) looks like a variant of the GM-30 (GMRS 30 channel) radio that is not yet supported.
Jim KC9HI
Updated by Bryant L 4 months ago
I have a MU-5 in my possession, what can I do to help this move along? Any special packet captures I can run? I don't know a lot about radios but I have an OEM programming cable, and work in the IT field with proficient access to both Linux and Windows copies of chirp. This radio seems to use similar software to the UV-13PRO, in fact it almost lets be clone the radio using the P15UV / UV-13PRO software, but fails when the model # doesn't match - probably for the better :)
I'd love just to have channel editing capabilities even... The CPS for the MU-5 is terrible, it forces all 100~ channels to exist at all times, and you cannot reorder the frequencies. This is a huge pain because in my use case MURS-1 is used by a local store, and I want to reprogram channel 1 to being channel 5, but the only way I can do that right now is just rename the channels, so 005 would = "Channel 1" and that's just confusing...
Updated by Bryant L 2 months ago
- File mu-5-tx.pcap mu-5-tx.pcap added
- File mu-5-tx-2.pcap mu-5-tx-2.pcap added
- File mu-5-rx-2.pcap mu-5-rx-2.pcap added
- File mu-5-rx.pcap mu-5-rx.pcap added
- File mu-5-cps.data mu-5-cps.data added
I took a stab at doing some USB captures, hopefully this can help get things rolling.
I am also willing to lend this radio out if it would help.
Updated by Dan Smith 2 months ago
- Tracker changed from Bug to New Model
- Subject changed from CHIRP Support for Radioddity MU-5 Radio to Radioddity MU-5
- Chirp Version deleted (
daily) - Model affected deleted (
Radioddity MU-5) - Platform deleted (
MacOS) - I read the instructions above set to Yes
- Equipment Loan/Gift Offered set to No
Updated by Steven Loomis 2 months ago
FYI here is the capture of a MU-5 using UV13Pro (i'm using an AIOC https://skuep.github.io/AIOC/ )
[2024-10-17 10:38:12,785] chirp.wxui.clone - DEBUG: Selected <class 'chirp.drivers.baofeng_uv17.UV13Pro'>
[2024-10-17 10:38:12,801] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2024-10-17 10:38:14,338] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2024-10-17 10:38:14,364] chirp.wxui.clone - DEBUG: Serial opened: Serial<id=0x116eb25c0, open=True>(port='/dev/cu.usbmodem032002e45', baudrate=57600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2024-10-17 10:38:15,875] chirp.drivers.baofeng_common - DEBUG: Wanted 8, got 0:
[2024-10-17 10:38:15,875] chirp.wxui.clone - ERROR: Failed to clone: Error reading data from radio: not the amount of data we want.
Traceback (most recent call last):
File "chirp/wxui/clone.py", line 92, in run
File "chirp/drivers/baofeng_uv17Pro.py", line 1081, in sync_in
File "chirp/drivers/baofeng_uv17.py", line 68, in _download
File "chirp/drivers/baofeng_uv17Pro.py", line 109, in _do_ident
File "chirp/drivers/baofeng_uv17Pro.py", line 101, in _sendmagic
File "chirp/drivers/baofeng_common.py", line 57, in _rawrecv
chirp.errors.RadioError: Error reading data from radio: not the amount of data we want.
Updated by Steven Loomis 2 months ago
Above was on Mac Sonoma.
post script - the CPS didn't work via the AIOC yet either, either in or out of a Win11 VM. I'll try with a BTECH USB programming cable and report back.