Bug #10450
closedGetting "Radio ID short" radio and cable work properly on another PC
0%
Description
I am a Mac user, I can program my BTECH UV-50X2 second gen and UV-25X4 fine from one Mac. Works from my desktop Mac. When I attempt to use my laptop, I get the "ID short" error every time I attempt to download the radio to the PC. I know the cable (PC-04) is good, and both radios are good. Can't figure out what is different on the laptop other than the OS (Big Sur working, High Sierra not). Log file attached.
Updated by Nick Hunseder over 2 years ago
I am a Mac user, I can program my BTECH UV-50X2 second gen and UV-25X4 fine from one Mac. Works from my desktop Mac. When I attempt to use my laptop, I get the " the extra ID is short, aborting " error every time I attempt to download the radio to the PC. I know the cable (PC-04) is good, and both radios are good. Can't figure out what is different on the laptop other than the OS (Big Sur working, High Sierra not). Log file attached.
Updated by Dan Smith over 2 years ago
- Status changed from New to Incomplete
This is almost definitely related to cables or drivers in some way. Also, Big Sur is the oldest release I'd really expect the current build to behave properly on, as that's the target system API being used for the builds. I assume you're using the exact same cable on the system that does and doesn't work right? Just because the cable works on another version of macOS (or windows for example) doesn't mean all that much.
Updated by Nick Hunseder over 2 years ago
Yes, the exact same cable is being used in both cases. That laptop isn't capable of going beyond High Sierra, so if that is a showstopper, I guess I'm stuck carting the radio in and out of the vehicle to reprogram.
Updated by Dan Smith over 2 years ago
- Status changed from Incomplete to Not a bug
Yeah, so the only difference in that case is the version of macOS, so it pretty much has to be that. It could be chirp being built for big sur and later, but I think it's far more likely that it's the USB-serial driver in the old macos. For a while there macos usb serial drivers were worse than windows, but things have gotten better in recent releases, so I'd tend to think it's that. It would be really unlikely that an interface as simple as reading from the serial port would partially work if it were a chirp-on-high-sierra type thing.
So, barring any other info, I'll mark this as not a bug, with the caveat that I feel your pain on having expensive apple hardware capable of running newer stuff but is prevented by policy :/