January 2021 - Users - lists.chirpmyradio.com

[chirp_users] "Download from radio" does not bring up clone window
by Mark Smythe 11 Jan '21

11 Jan '21

Windows 10 using Valley enterprises USB OPC-478 FTDI and installed recommended drivers. Cable plugged into PC and IC-2100H. I can not select serial port or radio without the clone window. Mark

3 9

[chirp_users] Puxing PX-2R "not responding"
by christoph＠grothesque.org 11 Jan '21

11 Jan '21

Hello, I’m trying to download the config from a Puxing PX-2R using Chirp 1:20190104-1 on Debian stable with the result that the "Radio is not responding". I searched the available information (wiki, bug reports, list archive) without finding a solution. Maybe someone here has a suggestion? The cable I use is shown by lsusb as Bus 002 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port When I connect the radio to the computer with this cable and switch it on, an orange LED lights above the active display. Since the radio does not react to key presses when connected in this way it seems to detect the connection. (When disconnected it reacts normally.) In chirpw, I select "Download from Radio" and Port: /dev/ttyUSB0 (the only one, read/write rights are OK) Vendor: Puxing Model: PX-2R Then I press "OK" and an error dialog appears together with the following message in the terminal: ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 256, in run self.__radio.sync_in() File "/usr/lib/python2.7/dist-packages/chirp/drivers/puxing.py", line 441, in sync_in self._mmap = puxing_2r_download(self) File "/usr/lib/python2.7/dist-packages/chirp/drivers/puxing.py", line 374, in puxing_2r_download raise errors.RadioError("Failed to communicate with radio: %s" % e) RadioError: Failed to communicate with radio: Radio is not responding ERROR: ---------------- ERROR: Clone failed: Failed to communicate with radio: Radio is not responding ERROR: --- Exception Dialog: Failed to communicate with radio: Radio is not responding --- ERROR: None ERROR: ---------------------------- I can reproduce the above with both PX-2R devices that I have access to. I read that PL-2303 cables normally do work on Linux. Does anyone have an idea what the problem could be? Thanks Christoph

2 1

[chirp_users] Import Error Regarding Radio Reference
by ctoci＠cox.net 10 Jan '21

10 Jan '21

Hello and thanks for what you do! Last week, I was successfully able to import frequencies from Radio Reference.com through my subscription. However, today, I was unable to do so. I have researched the FAQs regarding this topic. The only references I found were: CHIRP-Bug #4961 and Bug #4963. I downloaded the latest "Daily" version of CHIRP and tried import again with no success. Can you help? Thanks! Regards, Chris

1 0

[chirp_users] channel mode issues
by Tall Pine Construction 10 Jan '21

10 Jan '21

i looked thru faqs and lists didnt find info. i have 2 Baofeng uv-82hp radios and they will not switch to channel mode. i hold down menu button and switch off/on power. powers up everytime in frequency mode. i uploaded info to radios using chirp and can download from radios.

2 3

[chirp_users] New Daily Build
by Build System 10 Jan '21

10 Jan '21

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20210110 A list of the changes included in this build (since the last daily) follows: Changes for Build #642 [Dan Smith <dsmith(a)danplanet.com>] Remove errant ui import from anytone_iii driver The patch for #3941 imports a module from the UI for some reason, but does not use it. This seems to have been breaking the PPA build because we don't have gtk as a build-dep (for good reason). Drivers should be independent of the UI and are not allowed to import things from it. Since this driver wasn't actually using the import, removing it should be simple. Fixes #8493

1 0

[chirp_users] new radio
by Dee Burdette 08 Jan '21

08 Jan '21

I recently purchased a set of radios on Amazon. The info says the radio is programmable so I purchased a Baofeng cable (also recommended). The radio is not listed on the Chirp site as compatible. There is very little documentation with the radio and even less anywhere else. Any help is appreciated. ~Dee

5 4

[chirp_users] Chirp no work
by Billy Joe Higginbotham Jr 06 Jan '21

06 Jan '21

I can’t get my radio to link with my computer. I have the uv-5r and run Windows 7 on my computer. I keep get the message (An error has occurred could not open port [Error 2] The system cannot find the file specified.) It like the Chirp can’t see my radio. Sent from Billy’s IPhone

9 9

Re: [chirp_users] Chirp no work - on Windows, try Linux if possible
by Dave B 06 Jan '21

06 Jan '21

Hi. In Windows, after connecting the cable (no radio needed on the other end, nor Chirp running.) Go into the Device Manager, and look for the COM/Serial port device lists. If there are no Yellow Triangle signs, and you only see one COM port, that is the one you tell Chirp about. If you see more than one, with that display on screen, unplug the cable, wait, and re-plug it, and you'll see the list update so you can identify which COM port to use. If however, the one for your cable has a Yellow triangle, with a ! in the middle, then Windows as no driver for it, because it's recognised as either a counterfeit USB/Serial chip, or it's an old version of a Genuine chip (not uncommon sadly with Prolific chipsets) or a chipset that Windows does not know about (SiLab's and others typically, if so go to their website and pull the driver you need, for your version of Windows, and install it.) You can either rollback the driver, and install an earlier one. Under Win7 as you no longer receive updates, that should stick, but in effect your are then part of the problem stealing someone else's intellectual property by proxy. (Prolific's design and firmware.) On Win10, you will probably have to block updates else it will update to the current version that will again reject old/counterfeit devices, but in these troubled times, it is not a good idea to skip security updates. Just get a genuine FTDI or whoever's chipset based cable. OK, it costs more, but you don't need to block security updates and compromise your PC to keep using it. In Linux, the Kernel has all the drivers built in, and (usually, but for how long no one seems to say) they still work with the fake and old version chips too. (And very well too, it has to be said.) But... Your username must (On Debian based systems such as Ubuntu, Mint, Raspian and so on) be a member of the "dialout" group, or you will never get to use it. (Fedora bases systems I think have a similar requirement, but I don't know the incantation for them.) Open a command line window (Ctrl + Alt + T) and enter this:- sudo aduser $USER dialout You will be asked for your password (the same one you logged in with. '$USER' is a system variable containing your present login name.) After that you *MUST* Logout, and Log back In again (or reboot, if that is easier) for the change to take effect. Then you can use serial I/O devices. To find out what /dev/ttyUSB* number it has been assigned. Immediately after connecting the cable (again, no radio needed) in a command line window, use the command ls /dev/ttyUSB* That will show you all the USB/Serial devices it knows are connected. If you have several, compare the list without the programming cable, and with it connected, so you can identify which device name you tell Chirp to use. Note! In the presence of multiple USB/Serial devices, it is common for them to be "enumerated" (discovered) in a different order* when the machine is next restarted, so it is usually best to confirm what you have before starting the software! (* There are ways to make things consistent and stable, but that is beyond the scope of this email for now. If you are curious, look up 'udev rules' ) You may be able to "test" the cable, by connecting the apropriate pins of the radio end of the cable together, forming a serial loop-back, then you can use a terminal program (CuteCom for example, will need to install that if not already present) to type to yourself. See your radio's manual to identify which pins or terminals of the cable end to link.. Hope the above is not too much to digest. 73 Dave G8KBV On 06/01/2021 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Hi Billy > > I find that I can only get Chirp to work with my BaoFeng UV-5REs when I > do it with Linux. I get the same as you when I use Windows. It might be > the cable (I use the one I got when I bought the UV5REs), or it might be > the software, but if you can get access to a Linux you should be okay > even with a basic after-market cable. > > Kind regards, Mark Dixon, VK6EZ. > > On 6/01/2021 2:06 am, Billy Joe Higginbotham Jr via chirp_users wrote: >> I can?t get my radio to link with my computer. I have the uv-5r and run Windows 7 on my computer. I keep get the message (An error has occurred could not open port [Error 2] The system cannot find the file specified.) It like the Chirp can?t see my radio. >> >> Sent from Billy?s IPhone -- Created on and sent from a Unix like PC running and using free and open source software:

1 0

Re: [chirp_users] (None) Entries in Chirp
by bwmoore＠slidesnmoore.com 06 Jan '21

06 Jan '21

1 0

[chirp_users] (None) Entries in Chirp
by bwmoore＠slidesnmoore.com 06 Jan '21

06 Jan '21

4 3