- Users - lists.chirpmyradio.com

[chirp_users] New Daily Build
by Build System 04 Feb '21

04 Feb '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-20201221 A list of the changes included in this build (since the last daily) follows: Changes for Build #640 [Dan Smith <dsmith(a)danplanet.com>] Style fix related to patch for #8565 [Jim … [View More]Unroe <rock.unroe(a)gmail.com>] [H777] Retevis H777 Plus This patch adds support for the Retevis H777 Plus (FRS/PMR) models with fixed antennas. Related to #8565 [Jim Unroe <rock.unroe(a)gmail.com>] [H777] Rework Serial Timeout The previous patch has broken uploads for the classic BF-888s radios and newer Retevis H777 models. The constanstant switching of the timeout to .5 before each block is sent and back to .25 after each block is sent on a Windows computer creates "noise" that causes the apparently "faster" radios to mis the "ack" returned by the radio which results in the upload failing. This patch resolves the issue by setting the serial timeout to .5 and leaving it remain that way for all serial activity. fixes #8197 [Jim Unroe <rock.unroe(a)gmail.com>] [RT22] Remove FRS and PMR446 Frequency Tables This driver was coded in a way that erasing a memory row would preselect the appropriate FRS or PMR446 frequency, bandwidth and transmit power level. This would similar to how the OEM programming software functions (actually the OEM software has the frequencies, bandwidth and power level settings fixed so that they cannot be edited). While getting ready to submit test images for these models, I rediscovered that the CHIRP test suite regards this as a memory that can't be erased and reports an error. This patch removes the frequency tables and other code related to this so that the test suite will pass when tested with the related "image" files. related to #6467 [Jim Unroe <rock.unroe(a)gmail.com>] [RT22] Add Retevis RT622 Model This patch adds support for the Retevis RT622 PMR446 version. related to #6467 [Jim Unroe <rock.unroe(a)gmail.com>] [RT22] Add Retevis RT22FRS Model This patch adds support for the Retevis RT22 FRS version. related to #6467 [Jim Unroe <rock.unroe(a)gmail.com>] [RT22] Add Radio ID to Retevis RT22 Driver Add additional radio ID and supporting code that is required to support currently shipping Retevis RT22 models and other similar variants. related to #6467 [Jim Unroe <rock.unroe(a)gmail.com>] [RT22] Retevis RT22 Driver Cleanup for better PEP8 Compliance Clean up driver before adding another radio ID and support for additional radio models. related to #6467 [Jim Unroe <rock.unroe(a)gmail.com>] [KT-8R] Add New MCU Version This patch adds an additional MCU Version to the support for the QYT KT-8R fixes #8513 [Brad Schuler <brad(a)schuler.ws>] [anytone_iii] Naming convention cleanup (issue #8503) [Mark Leigh <mark.leigh(a)shaw.ca>] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal. user: Mark Leigh <mark.leigh(a)shaw.ca> branch 'default' changed chirp/directory.py changed chirp/radioreference.py changed chirp/ui/mainapp.py [View Less]

11 16

[chirp_users] Yaesu FTM-400XD
by Mike Markowski 03 Feb '21

03 Feb '21

In the hope of supporting the ftm-400xdr, over the course of 2 months I wrote twice to Yaesu asking if a programming guide is available. Both times, no reply. Yet their tech support replies quickly (relatively speaking!) to other questions. Does anyone know of a source for the info, better email address, etc.? Tnx es 73! Mike ab3ap

2 1

[chirp_users] Yaesu FT-2600M, FT-2800M
by Michael Tortorella 01 Feb '21

01 Feb '21

Has anyone tried to use the FT-2800M programming procedure for the FT-2600M? Thanks for any input, 73, Mike W2IY

1 0

Re: [chirp_users] Packaging Changes...
by Dave Felt 01 Feb '21

01 Feb '21

Dear Michael, Sure, whatever you have to do to stay in businesss.. Dave

1 0

[chirp_users] Alinco DJ-VX50
by GRAND WILDLIFE CONTROL 24 Jan '21

24 Jan '21

Greetings! And thank you for this fine product. We're seeking information/ support regarding the Alinco DJ-VX50. Will there be a platform for programming this radio through CHIRP? Thanks kindly

2 1

[chirp_users] Baofeng Kenwood TK3201
by Remi Kemperman 24 Jan '21

24 Jan '21

Hi Has somebody for me a file withe the correct channels from a Kenwood TK3201 to uploas in a Baofeng? I have placed them manually, but I can hear the Kenwood sending, but the Kenwood does not receive the Baofeng. Thanks

4 5

[chirp_users] USB cable help
by Marc Danziger 20 Jan '21

20 Jan '21

I've tried the various drivers I can find online, but neither Chirp nor the Baofeng app can seem to establish communication... Is there a robust FAQ somewhere on this or someone who can guide me through?? Marc - ham in waiting

5 4

[chirp_users] Baofeng UV-5R MK4
by ken smith 13 Jan '21

13 Jan '21

I have successfully been able to use Chirp to upload .csv files etc. All communications between the software and radio seem to work. However, when manually loading HAM repeater information, the upload info seems to not take correctly. For example, I used the software to put in a 2m frequency, no tone, “-“ offset at 0.60 and low transmit power. After the upload, the radio shows the correct frequency and memory name but that’s it. The transmit power shows Medium (which isn’t even an option in the … [View More]

4 7

[chirp_users] Channel Transfer
by Bennie Potgieter 13 Jan '21

13 Jan '21

Gooday I want to have my baofeng and Kenwood to comunicate on thw same chanels (Baoffeng chanels), as the kenwood is only VHF. Can someone help me wit step by step or screenshots to help me in this please Im not that big on the programming everyday. Thank you

1 0

[chirp_users] Puxing PX-2R "not responding"
by Dave B 12 Jan '21

12 Jan '21

Hi Christoph. If you look in the bug report page:- https://chirp.danplanet.com/issues/6389 that I instigated a while ago... (Probably needs a login, begin at https://chirp.danplanet.com/login ) It seems from what one of the dev's has said:- Looks like the number of DCS codes reported by the radio exceeds what Chirp expects or can handle. Guess we have to look into this. That was 8 months ago, and as I was the only one reporting a problem, I guess it's a low priority. If you … [View More]could login and add your voice to the report, maybe, something might happen. But, I suspect most of the dev's are working to get CHIRP working on Python3.x rather than fixing low profile bugs like this. (NOT a flame, just how it goes, and I understand why that is hopefully a priority.) I can do a little Python programming, but CHIRP is a huge codebase, and trying to understand one model of radio's back end, in isolation of the rest, is nigh on impossible for me. Else I'd have a go, but from Bernhard's comment, the problem could be deeper within CHIRP, rather than the radio's driver/backend code. 73 All. Dave G0WBX. On 11/01/2021 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Date: Mon, 11 Jan 2021 11:56:18 +0100 > From:christoph@grothesque.org > Subject: [chirp_users] Puxing PX-2R "not responding" > To:chirp_users@intrepid.danplanet.com > Message-ID: <878s8z214d.fsf@drac> > Content-Type: text/plain; charset=utf-8 > > 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 -- Created on and sent from a Unix like PC running and using free and open source software: [View Less]

2 1