tapegugl.blogg.se

1. Baofeng 888s programming mac os x#
2. Baofeng 888s programming drivers#
3. Baofeng 888s programming driver#
4. Baofeng 888s programming windows 10#
5. Baofeng 888s programming software#

Baofeng 888s programming drivers#

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.

Baofeng 888s programming windows 10#

Baofeng 888s programming software#

Using the BF-888s software gives me the error some have experienced where it only programs the first half of the channels but it does communicate with the 888s - and using the ZT-V68 software all channels program properly - so it doesn't appear it's a limitation of the cable being able to communicate with the 888s.

HOWEVER, that cable + CHIRP DOES readily program two UV-5R devices that I bought at the same time.Īdditionally, the same cable does program the 888s devices with the OEM software on Miklor's page. I am using this cable (probably a knockoff). I have four new 888s devices, zero of which connect - all producing the "Radio refused to enter programming mode" as described above. I ended up here after going through much of the same experience. That is why the cable with the CH-35 chip read the new radios fine. That is why both radios downloaded fine on my Linux Mint 17.3 computer.Īn alternative to messing with drivers is to switch to a programming cable with a chip from a different manufacturer. Linux users don't have to worry about it because their drivers for the PL-2303 chip.

Baofeng 888s programming driver#

For El Capitan and later, I have heard of successful results from those purchasing a 3rd party driver from Repleo for €7.90 (approximately $8.23).

Baofeng 888s programming mac os x#

Mac OS X users prior to El Capitan have to install one of the generic drivers linked to on the MacOS_Tips page. The v3.2.0.0 driver is the one I use in Windows 7 64-bit computer that I use for CHIRP development and my Windows 10 virtual machine (and why both Mark's new BF-888s radio and my older radio work fine). What Windows users must do is download, install and select the older Prolific v3.2.0.0 driver for Vista, 7, 8 and 10 (v2.0.2.1 for XP) that was available before the drivers were change to not cooperate with counterfeit Prolific chips. Apparently the newer BF-888s radios are no longer tolerant (the same as nearly every other radio has always been). Recently (within the last year of so) the driver was updated to complete the install but to still not operate properly with a counterfeit chip.Īpparently the older BF-888s radios were tolerant to whatever the device driver does to be incompatible with the counterfeit chip. The Windows device driver installation used to fail with an error code 10 when a counterfeit chip was detected. At around this time is when they became intentionally designed to be incompatible with counterfeit in hopes to curb the use of these chips. Especially the Baofeng branded one and and I would expect the Retevis branded one as well.), Windows and Mac users must not use the Prolific written drivers that have been available since about 2008. When you have a programming cable with a counterfeit Prolific PL-2303 chip (nearly all programming cables that report they are a Prolific chip to the OS are counterfeit. It has to do with an incompatible device driver. RadioError: Radio refused to enter programming mode Raise errors.RadioError("Radio refused to enter programming mode") chirp.ui.common - ERROR: Traceback (most recent call last):įile "/Applications/chirp.app/Contents/Resources/chirp/chirp/ui/clone.py", line 249, in runįile "/Users/gerhard/Downloads/h777.py", line 288, in sync_inįile "/Users/gerhard/Downloads/h777.py", line 187, in do_downloadįile "/Users/gerhard/Downloads/h777.py", line 111, in _h777_enter_programming_mode chirp.ui.reporting - DEBUG: Reporting exception chirp.ui.clone - DEBUG: Clone thread started chirp.ui.mainapp - DEBUG: User selected Baofeng BF-888 on port /dev/cu.usbserial chirp.directory - INFO: Registered Baofeng_BF-888 = H777Radio chirp.directory - WARNING: Replacing existing driver id `Baofeng_BF-888' chirp.directory - INFO: driver re-registration enabled I have tried the attached module but still nothing. Works fine with the official software on windows, but no go on Mac with latest chirp daily from. I am getting the exact same issue with recently purchased BF-888s radios.