July 2019 - Users - lists.chirpmyradio.com

Re: [chirp_users] Yaesu 3200D and RT Systems cable problem
by JOCK SOUTAR 26 Jul '19

26 Jul '19

I have some software and cables from RTsystems and I have used their cables for many years and have never had any problems with them. Jock. KC6IIH On Friday, July 26, 2019 Nigel A. Gunn G8IFF/W8IFF <chirp_users(a)intrepid.danplanet.com> wrote: No, but their software only works with their cable. RT cables work OK with Chirp, On 26 July 2019 at 12:17 John La <Johnla(a)usa.net> wrote: Is it possible the RT cable is proprietary to their software only? John K3NXU www.Miklor.com -----Original Message----- From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jan Ditzian Sent: Thursday, July 25, 2019 8:27 PM To: chirp_users(a)intrepid.danplanet.com Subject: [chirp_users] Yaesu 3200D and RT Systems cable problem I have an RT Systems Yaesu programming cable for a Yaesu FT-1900 two-meter mobile radio that fits my new FTM-3200D radio. I installed the latest Chirp, as of today, and it knows about the FT-3200D. I plugged the cable into the computer USB and the radio microphone jack. By trial and error, I discovered that the FTM-3200D goes into CLONE mode by holding in SETUP and then turning it on. Also, by trial and error, I found that the FTM-3200D went into TRANSMIT mode to the computer by starting the Chirp Download from Radio, and then pressing REV on the FT-3200, whereupon the radio went to TX mode and began to count up, and Chirp also showed that it was downloading data. The process finished, the radio went back to CLONE, but Chirp returned a checksum error. Chirp does not display any radio data after the failure. To sum up, the radio is happy that it spoke to Chirp, but Chirp is not happy with what it heard, probably at the end of the exchange. Does anyone know how I can get past this error message? Thank you and 73, Jan, KX2A _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to John LaMartina at johnla(a)usa.net To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel(a)ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih(a)aol.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Yaesu 3200D and RT Systems cable problem
by Jan Ditzian 26 Jul '19

26 Jul '19

I have an RT Systems Yaesu programming cable for a Yaesu FT-1900 two-meter mobile radio that fits my new FTM-3200D radio. I installed the latest Chirp, as of today, and it knows about the FT-3200D. I plugged the cable into the computer USB and the radio microphone jack. By trial and error, I discovered that the FTM-3200D goes into CLONE mode by holding in SETUP and then turning it on. Also, by trial and error, I found that the FTM-3200D went into TRANSMIT mode to the computer by starting the Chirp Download from Radio, and then pressing REV on the FT-3200, whereupon the radio went to TX mode and began to count up, and Chirp also showed that it was downloading data. The process finished, the radio went back to CLONE, but Chirp returned a checksum error. Chirp does not display any radio data after the failure. To sum up, the radio is happy that it spoke to Chirp, but Chirp is not happy with what it heard, probably at the end of the exchange. Does anyone know how I can get past this error message? Thank you and 73, Jan, KX2A

3 3

[chirp_users] Programming Baofeng UV-9
by William Thompson 23 Jul '19

23 Jul '19

I'm helping a group program their new radios. They have Baofeng UV-9, not 9R, but UV-9. There are no manufacture labels except in the battery compartment. It appears to be a UV-5R variant as it incorporates the Kenwood standard 2-pin plug and a 5R spkr-mic works with the radio. I'm using the same cable that I use with my 5R but the radio fails to respond to Chirp no matter what radio model I use in the Baofeng and BTECH listings. Is there a preferred for this radio. By the way, it doesn't show a firmware version on power-up. 73, William

3 2

[chirp_users] Baofeng UV-82HP Programming Issues (MacOS Mojave 10.14.5)
by Brennan Stanford 23 Jul '19

23 Jul '19

I am having issues using CHIRP to program my brand new Baofeng UV-82HP. I have an FTDI cable and am using a Mac (MacOS Mojave 10.14.5) and CHIRP 7.13.2019. I have zero problems with downloading from and programming to my BF-F8HP, but the UV-82HP will not work. Every time I connect to the radio and attempt to do the original image download, the radio restarts itself, and then CHIRP then gives me “Radio did not respond” error. Brennan J. Stanford office: 419.740.0513 mobile: 419.450.7290 email: bjstanf(a)gmail.com

4 4

[chirp_users] Can't Upload to BTech VV-5X3
by Dave Hartman 22 Jul '19

22 Jul '19

I don't know if this is a Chirp issue or a winDOZE 10 issue. Back in March 2019 things worked great. Today 7/21/19 I downloaded the chirp-daily-20190718-installer.exe and attempted to install it. I got several unable to write file errors. So I downloaded it again and tried to install again but with the same problem. So I uninstalled it, and installed the chirp-daily-20190319-installer which had worked just fine last last March. Again no joy. With either version I can download from the radio without issue but just can't upload to it. Next I'm going to uninstall it again, using Revo Uninstaller reboot my machine, and try it again with my Wouxun KG-UVD1P. If anyone has had this problem, please let me know how you solved it. Thanks! -- Dave - AC2GL All typing errors are my own work and subject to copyright laws, except errors by the spell checker which are open source errors.

3 2

[chirp_users] New Daily Build
by Build System 18 Jul '19

18 Jul '19

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-20190718 A list of the changes included in this build (since the last daily) follows: Changes for Build #587 [Dan Smith <dsmith(a)danplanet.com>] Correct Baofeng->Radioddity brand for UV-82X3 Related to #6921 [Rick DeWitt <aa0rd(a)yahoo.com>] [th_uv8000] Fix to tuning steps; issues #6909 and #6913 Fixes #6909 and #6913 are due to needing rf.has_nostep_tuning enabled [Dan Smith <dsmith(a)danplanet.com>] Correct 82X3 to UV-82X3 model name Related to #6921 [Dan Smith <dsmith(a)danplanet.com>] Add support for Baofeng 82X3 Fixes #6921

1 0

[chirp_users] New Daily Build
by Build System 13 Jul '19

13 Jul '19

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-20190712 A list of the changes included in this build (since the last daily) follows: Changes for Build #585 [Dan Smith <dsmith(a)danplanet.com>] Add future to tox config Related to #743 [Dan Smith <dsmith(a)danplanet.com>] Add Kenwood TK-8180 driver #743 [Dan Smith <dsmith(a)danplanet.com>] Make run_tests handle sub_devices in the same way the main app does, which is by using the instances returned directly, instead of expecting them to be re-initializable by class and filename. This is needed for the tk8180 driver, which requires more tight coupling between the parent instance and the instances of the sub_device instances. Related to #743 [Dan Smith <dsmith(a)danplanet.com>] Add memmap compatibility with py3 branch This merely adds an interface for MemoryMapBytes to memmap so that code that works on both branches can reference the byte-clean variant here. Otherwise it is basically just an alias. Related to #743 [Dan Smith <dsmith(a)danplanet.com>] Add image for TH-UV8000 from Rick for #2837 [Rick DeWitt <aa0rd(a)yahoo.com>] [th-uv8000] New driver for TYT TH-UV8000 family, fixes issue #2837 Submitting new driver in support of 11 issues 2837 ... 6183

8 8

[chirp_users] Kenwood TM-V7A problem
by William Mooney 13 Jul '19

13 Jul '19

I have a Kenwood TM-V7A connected to a Mac Mini running OS X Mojave 10.14.5. The cable has a FT232R USB UART chip. I downloaded the latest driver from FTDI and the latest Daily Build. The computer sees the cable, but CHIRP does not. Download from radio says no file. All was working fine before the Mojave upgrade. Help? Bill sends. Bill Mooney 33100 Highway 300 Bigelow, AR 72016 501-330-2843 mooney6(a)me.com W5WMM (the wireless giant of Wye Mountain)

1 0

[chirp_users] New Daily Build
by Build System 13 Jul '19

13 Jul '19

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-20190713 A list of the changes included in this build (since the last daily) follows: Changes for Build #586 [Dan Smith <dsmith(a)danplanet.com>] Additional settings support for TK8180 Also, avoid registering if we are unable to import the future module. A gross hack for now, which will make this driver unavailable in the MacOS build currently, but this is the easiest solution to the much larger problem of not being runnable at all. Related to #743 Fixes #6095

1 0

[chirp_users] TYT UV8000D marked closed but not in daily
by Jeff 09 Jul '19

09 Jul '19

I saw on 7/3 the UV8000D/E drivers were marked completed and a daily build was made the same day however no drivers were pushed to source control. Possible mix up on status? Or code not pushed?

1 0