- Users - lists.chirpmyradio.com

[chirp_users] Kenwood NX329
by beachwoodpeter＠gmail.com 16 Aug '16

16 Aug '16

Any chance someone will add the Kenwood NX series radios? Like the NX320. Peter Wilcox Beachwood Productions Beachwoodproductions.com > On Jul 7, 2016, at 12:16 PM, William Thompson via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: > > I'm helping a friend program his new Baofeng BF-F0V2+ and n we're receiving a "experimental firmware error". Has a version been released for this radio? > > 73, > Bill > KK4ZIU > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Peter at beachwoodpeter(a)gmail.com > To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] New Daily Build
by Build System 16 Aug '16

16 Aug '16

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-20160816 A list of the changes included in this build (since the last daily) follows: Changes for Build #424 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-5R] Add Support for UV-6 with Longer 12 byte Ident The currently shipping Baofeng UV-6 responds to the clone request by returning a 12 byte "ident". The original model replies with an 8 byte "ident" (the same as all other radios currently supported by the uv5r.py driver). The current CHIRP driver appends the radio's memory image after the "ident" so the settings structures are all offset by 8 bytes to accomodate these extra bytes at the beginning of the image. So there must alway be exactly 8 bytes prepended to the actual memory map data. Original UV-6 ident: AA 36 74 04 00 05 20 DD New UV-6 ident: AA 01 01 36 01 74 01 04 00 05 20 DD This patch works around the issue by doing the following... 1. The "ident" is now read one byte at a time until the last byte ("\xdd") is received. This make it compatible with an 8 byte and 12 byte "ident". 2. The 4 bytes of the ident containing "\x01" are discarded to shorten the ident to the standard 8 byte length and to put the "ident" in the same format as the "ident" of the other radio models. Related to Bug #3063

1 0

[chirp_users] New member with a couple questions
by Glenn 15 Aug '16

15 Aug '16

Hi, My name is Glenn, I live in Nebraska. I have a UV-5R, and my son has a BF 8HP by Baofeng. I should mention that I am using Chirp on computers with a screenreader for the visually impaired. One computer is running Windows 7, and the other is running Ubuntu 16.04. I tried to connect the BF8HHP to my Ubuntu with the hopes of uploading all my programming from my 5R to it, and I keep getting the message: an error has occurred failure to communicate with radio serial object has no attribute 'setTimeout' I am using USB0 with a Baofeng cable. So with this issue, I switched to doing this on my Windows computer, but I don't like that much, because it is quite difficult using the program with a screenreader in Windows. But I successfully exported my 5R to a CSV file. Then I connected the 8HP and imported the 5R file, and then tried to upload it to the 8HP, and in the radio list, the make and model selections are grayed out, and it only shows the UV-5R. I tried to proceed with the upload anyway, but it would not let me. This is the steps for this procedure in the on-line help, even for two different radios. Maybe I missed something? Thanks for any assistance. Glenn

4 6

Re: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect...
by Angus Ainslie 13 Aug '16

13 Aug '16

On 2016-08-06 08:09, David McGuire wrote: > python-serial: > Installed: 3.0.1-1 > Candidate: 3.0.1-1 > Version table: > *** 3.0.1-1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 > Packages > 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 > Packages > 100 /var/lib/dpkg/status > Please reply all when asking questions in the list That looks correct as well but chirp had an issue with pySerial v3 http://chirp.danplanet.com/issues/3167 So it looks like you need to update chirp

2 3

[chirp_users] New Daily Build
by Build System 13 Aug '16

13 Aug '16

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-20160813 A list of the changes included in this build (since the last daily) follows: Changes for Build #423 [Tom Hayward <tom(a)tomh.us>] [RadioReference] Fix Chirp crash on empty scName attribute. #881

1 0

[chirp_users] Kenwood TK-762H
by Tim Billingsley 11 Aug '16

11 Aug '16

I have a couple of old Kenwood TK-762H transceivers. I see the issue on http://chirp.danplanet.com/issues/3139 but I seem to be having troubles. When I attempt to read from the radio using TK-762G it appears to read from the radio then dumps the error dialog *"An error has occurred: The radio doesn't accept program mode"* ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760g.py", line 884, in sync_in self._mmap = do_download(self) File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760g.py", line 517, in do_download _open_radio(radio, status) File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760g.py", line 478, in _open_radio raise errors.RadioError("The radio doesn't accept program mode") RadioError: The radio doesn't accept program mode ERROR: ---------------- ERROR: Clone failed: The radio doesn't accept program mode ERROR: --- Exception Dialog: The radio doesn't accept program mode --- ERROR: None ERROR: ---------------------------- If I attempt using TK-760 chirp attmpts to read and almost immediately dumps the error dialog saying *"An error has occurred Radio refuse to enter into program mode after a few tries"* ERROR: ---------------------------- ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760.py", line 411, in sync_in self._mmap = do_download(self) File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760.py", line 255, in do_download open_radio(radio) File "/usr/lib/python2.7/dist-packages/chirp/drivers/tk760.py", line 227, in open_radio raise errors.RadioError(msg) RadioError: Radio refuse to enter into program mode after a few tries ERROR: ---------------- ERROR: Clone failed: Radio refuse to enter into program mode after a few tries ERROR: --- Exception Dialog: Radio refuse to enter into program mode after a few tries --- ERROR: None ERROR: ---------------------------- FWIW I am running CPU~Dual core AMD E2-1800 APU with Radeon HD Graphics (-MCP-) speed~1700 MHz (max) Kernel~4.2.0-34-generic i686 Mem~2035.9/3635.1MB HDD~750.2GB(35.9% used) Ubuntu 15.10 CHIRP daily-20160513 GTK 2.24.28 PyGTK 2.24.0 Python 2.7.10 I am also having issues with a QTY KT8900 I have tried to follow all this has been discussed on http://chirp.danplanet.com/issues/2673 but to no avail. any assistance is appreciated

8 18

[chirp_users] General: Updating CHIRP
by Richard B. Emerson 11 Aug '16

11 Aug '16

How are non-alpha/beta updates handled? That is, given all the daily releases (i.e., alpha testing), is there ever a "looks pretty stable to me" release? What I've got now does what I need done (very well - good on ya!). OTOH, a new release might do something useful that I don't have in the release I use. But I prefer not to do alpha or beta testing if I can avoid it. So... how often does a stable release come out? 73 de KC3DOO Rick

4 5

[chirp_users] yaesu ft 2800m
by fergy1 11 Aug '16

11 Aug '16

chirp just will not read header or communicate with radio tried ftdi cables plus serial cables chines cables 3 xp computers plus win 7 run chip check cables show up good radio goes to clone then comes up error chirp says cant read header error cables all work with ft 1802 all other radios program fine must be a weird ft 2800 been trying to program this radio for over 10 years tired of programming manually ill send the bug attachment if any one can figure out whats going on thanks --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

[chirp_users] removel of Plan
by bernard.dowley＠sky.com 11 Aug '16

11 Aug '16

Hi Using Chirp with either a Baofeng UV-5R or Intek KT 980HP is it possible to remove the 2 metre and 70 centimetre facility so that only the user programmed frequencies are available for use. Any help appreciated Regards BernieBernard Dowley

4 9

[chirp_users] Baofeng data to Yaesu
by djkwasny＠aol.com 10 Aug '16

10 Aug '16

Hi, I am trying to move Baofeng data to a Yaesu ft-7900R. If I load the Baofeng data into Chirp It selects Baofeng in the upload box and I cannot change it as it is grayed out. Any help anyone can provide will be appreciated. Thanks, Joe - K5WAS

5 5