September 2018 - Users - lists.chirpmyradio.com

[chirp_users] power settings in CHIRP
by Glenn At Home 30 Sep '18

30 Sep '18

Hi, I have a Baofeng HP F9 V2+, I think I got that right, anyway, I want to make sure all power levels are on high, in CHIRP, and I don't find a column that indicates that. I have some blank columns, would it be one of those? Thanks. Glenn Sent From My Tabletop

2 4

[chirp_users] FT-450D communication problem
by Bruce Ashdown 30 Sep '18

30 Sep '18

I have just downloaded latest Chirp (CHIRP daily-20180906). Using Windows 10, Com port 3, Vendor Yaesu, Model FT-450D. My CAT cable works fine with "PCC for FT-450D", WSJT-X , "Ham Radio Deluxe" & "FREE450", but not "Chirp"! Followed instructions to download from radio & got message:- An error has occurred - Failed to communicate with radio: Unable to read block 0 expected 6 got 4. Any ideas? My FT-450D has the UK 60m frequencies plumbed into the memories - will these be saved in Chirp? I want to update the radio's firmware, so want to backup the memories including the 60m ones. Thanks

4 3

[chirp_users] New to CHIRP and issue with Baofeng
by Berrie Maas 28 Sep '18

28 Sep '18

Hi, I am new to CHIRP, and a fairly new HAM as well. I have CHIRP installed, and try to connect to my BAOFENG UV-82. CHIRP will not let me select a COM port. I am using the cable that BAOFENG sells. The cable came with a disk, but it is in Chinese, and when I try to change the setting to English, it says it cannot write to the disk. Starting the BAOFENG software (BF480), it is all in Chinese and with question marks as I don't have Chinese fonts. It probably is a driver issue, but I don't know where to get the right driver. Any help greatly appreciated! Berrie

3 2

[chirp_users] Can't program or read Retevis RT-22
by Jaye Mathisen 27 Sep '18

27 Sep '18

Read through the last couple months of archives, didn’t see anything directly related. Using the latest chirp, I cannot program or read from a retevis RT-22. Used to clone them all the time, then we didn’t need any for a while, got a new batch, and all I get when I try to read is an “unknown identification string”, and if I try to download programming from the img file we were using before, I get an error about 5 tries, but haven’t been able to get that to come up again. If I load the RT22 software downloaded from retevis, it fires right up, and can at least read the radio config, I haven’t tried writing it again. I programmed some RT22’s about 2 months ago, and didn’t have any of these issues, so I’m not sure if it’s a retevis firmware change, or what. Debug.log is attached. Thanks for any help. *--* *Jaye Mathisen* *Lil Pantry* *Ph: 541-476-0152 / Fax: 541-476-0152* -- This electronic message may contain information that is privileged, confidential or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic message or its contents by persons other than the intended recipient(s) is strictly prohibited, and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender so that we may correct our internal records, and then delete the original message.

2 2

[chirp_users] Alinco DR-235T - "No response from radio" Error
by Justin Dawson 24 Sep '18

24 Sep '18

I found this old bug report from several years ago that I thought might address my issue: https://chirp.danplanet.com/issues/254 I tried changing the baud rate for the COM port I'm using, but it made no difference. I get the same error whether I'm in clone mode or not. Any ideas?

2 1

[chirp_users] Decoding BaoFeng 6+Power-On Message ?
by Peter 24 Sep '18

24 Sep '18

Some BaoFeng radios include a "6+Power-On Message" which can be displayed by holding down the 6 key while powering on the radio. These message strings are stored in "6+Power-On Message" lines 1 & 2 as displayed by CHIRP in "Settings" > "Other Settings". Line 1 of the "6+Power-On Message" is apparently included (in parentheses) in the filenames of some of the CHIRP recovery images maintained at Jim's site, here: http://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/ For example, "N82-33 US2S35(150602N)(factory).img" includes "(150602N)" in the filename. I believe this image applies to the BaoFeng UV-82HP, and one of these units I own did include "150602N" in line 1 of the "6+Power-On Message". I say "did" because apparently this string is cleared by resetting the radio to factory defaults via MENU > 40 > RESET > ALL. Anyway, these strings look suspiciously like manufacturing date codes. For example, 150602N would decode to 2015-06-02, which is just a few months before the "Last modified" file date of 12-Oct-2015 (as displayed in the CHIRP recovery image listing in the web browser). As far as I can tell, for *all* of the files in the CHIRP recovery images directory which include such a string , that string decodes to a date that is a few days to a few months prior to the "Last modified" date. And in no case does any such string decode to a date that is later than the "Last modified" date. Can anyone confirm that these strings do indeed represent manufacturing date codes? Also, does anyone have a radio that still displays this "6+Power-On Message" after resetting the radio to factory defaults? Thanks... (Peter)

3 5

Re: [chirp_users] chirp_users Digest, Vol 117, Issue 16
by Dave B 24 Sep '18

24 Sep '18

Indeed, so why are we indirectly promoting the use of counterfeit devices then? If the chip is "Genuine", the currently available "Official" driver, /will/ work. Yes, I too have accumulated some dodgy chip driven adapters, just as everyone I suspect has. I am slowly replacing them as I find them, not because they don't work (they work just fine under Linux, for now.) But because they all have the same identity and no serial number, making the use of multiple devices and nailing their feet to the numeric floor with Udev rules, rather troublesome. I prefer FTDI parts, as by default they all have a unique serial number, making Udev rules easy and reliable. SiLabs parts are a close second choice*, with Prolific only if there is absolutely no other alternative. Even the genuine Prolific chips don't seem to have a "unique" identity. (Unless I've not yet seen a "Genuine" chip!) General Linux trick: What I've found is that if you build a Udev table for regularly connected devices, starting from /dev/ttyUSB1 (or higher) then anything else that is randomly connected later, will always show up as ttyUSB0 or 2 etc, as they is still vacant. End. 73. Dave G0WBX. On 23/09/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > I don't think you will find the older v3.2.0.0 driver available for > download on the Prolific site. -- Created on and sent from a Unix like PC running and using free and open source software. ::

4 3

Re: [chirp_users] Baofeng Programming Cables - Solved
by Richard AG5M 24 Sep '18

24 Sep '18

Problem solved. I installed the 3.2.0.0 into Windows 10 from Miklor web site. All is well. Never had any problem with Windows XP or Windows 7, until I tried it on my Windows 10 laptop. I'm never getting rid of those older computers. 73, Richard AG5M -------------------------------------------- On Thu, 9/20/18, Jardy <jardy72(a)yahoo.com> wrote: Subject: Re: [chirp_users] Baofeng Programming Cables To: "Richard AG5M" <ag5m(a)yahoo.com>, "Discussion of CHIRP" <chirp_users(a)intrepid.danplanet.com> Date: Thursday, September 20, 2018, 6:36 PM Windows 10 updates the Prolific driver to one that makes some Prolific cables not work. These cables have fake chips in them. Roll back your driver to 3.2.0.0. It will work then. For driver info, go to www.miklor.com. Jardy Dawson WA7JRD

5 4

Re: [chirp_users] Baofeng Programming Cables - Solved
by Peter 24 Sep '18

24 Sep '18

I already have the BTECH FTDI cable, thanks Bryan. And I've never had a problem with the drivers that Windows Update provides for the FTDI chipset on Windows 10. I'm just offering Microsoft's "driver rollback prevention solution" (below) for whomever might want it, for whatever device. It's a way to prevent driver updates for specific devices, as opposed to preventing all updates for all devices, or disabling Windows Update entirely (which is not a good idea). On 9/24/2018 12:32 AM, bsantucci wrote: > Peter, > > get this cable! no drivers needed, nothing to do plug it in done! > > https://www.amazon.com/gp/product/B00HUB0ONK/ref=oh_aui_search_detailpage?i… > > > > Sent from my Sprint Samsung Galaxy S9+. > > -------- Original message -------- > From: Peter <ptlambert(a)sbcglobal.net> > Date: 9/24/18 03:27 (GMT-05:00) > To: chirp_users(a)intrepid.danplanet.com > Subject: Re: [chirp_users] Baofeng Programming Cables - Solved > > I gave up trying to swim upstream in Microsoft's river. Either go with > the flow or jump ship to Linux. :@) > > Seriously, there are "supported" methods in Windows 10 to prevent > Windows Update from undoing your successful driver rollback. This > method is the easiest I've found for folks that would rather not dig too > far under the hood of the Microsoft bus: > > https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent… > > > On 9/23/2018 2:08 PM, Richard AG5M via chirp_users wrote: > > Problem solved. I installed the 3.2.0.0 into Windows 10 from Miklor > web site. All is well. Never had any problem with Windows XP or > Windows 7, until I tried it on my Windows 10 laptop. I'm never > getting rid of those older computers. > > 73, Richard AG5M > > > > -------------------------------------------- > > On Thu, 9/20/18, Jardy <jardy72(a)yahoo.com> wrote: > > > > Subject: Re: [chirp_users] Baofeng Programming Cables > > To: "Richard AG5M" <ag5m(a)yahoo.com>, "Discussion of CHIRP" > <chirp_users(a)intrepid.danplanet.com> > > Date: Thursday, September 20, 2018, 6:36 PM > > > > Windows 10 > > updates the Prolific driver to one that makes some Prolific > > cables not work. These cables have fake chips in them. Roll > > back your driver to 3.2.0.0. It will work then. For > > driver info, go to www.miklor.com. > > > > Jardy Dawson > > WA7JRD > > _______________________________________________ > > 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 ptlambert(a)sbcglobal.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 Bryan Santucci at bsantucci(a)aol.com > To unsubscribe, send an email to > chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

Re: [chirp_users] Baofeng Programming Cables
by Dave B 23 Sep '18

23 Sep '18

Quiet frankly, better to go to the chipset makers own website and get the correct and likely mallware free ones. Not to say Miklor website is bad, but it's just another third party website with a collection of files, that "could" not be safe. They might also not be the latest copies of the official drivers. I'm sure they (whoever "Miklor" are) take care to keep things clean, but they would not be the first or only site to have their repository of useful stuff compromised. http://www.miklor.com/COM/UV_GettingStarted.php States the situation very well. However, they wrongly state that FTDI devices don't have that problem. Sorry, but yes they do, there are just as many fake FTDI chips out there as Prolific! The difference is that the official drivers will usually work with them*. But, if you need to alter their behavior (the handshake or status lines, or "which way up" the data lines work) then you'll find that functionality is missing from the fake chips. * FTDI a while ago did create a storm however, by putting code in the "official" drivers, that could detect the fakes and in turn reprogram the VID/PID info to all zero's rendering them unusable. It is however possible to re-program that information, but it takes some research plus confidence with command line tools on a Linux PC. (As far as I know, the tool for that isn't, or wasn't available for Windows. I can't even remember what it's name is either.) FTDI soon after, then pushed out a driver that did not disable the things, but for all we know, it may report back to FTDI, or somewhere, any instances of fake chips. No, I did not say they DO that, just that they could. If it was my IP that was ripped off, I'd want to know how bad the problem was, and that would be a way to find out. The Fake chips are actually micro-controllers programed to emulate the real devices. That they do amazingly well, but not 100%. I have encountered some that were marked up as FTDI, but were functioning as Prolific devices! The supplier I used had no idea, but did apologize and gave me a full refund on the return of the stock I bought for a work project. I wouldn't trust Amazon either to only ship non-counterfeit cables either! In Amazon's defense, it's often not their fault, and often the actual vendor doesn't know either! (See above...) I usually make up my own cables using known good modules from the makers themselves, or from known reputable resellers. It's not difficult, and you learn stuff too. (Isn't that what we're supposed to be doing?) The SiLabs USB/Serial bridge products are also very good, and as yet(?) Not counterfeited, unless someone knows different. Take care. 73. Dave G0WBX On 22/09/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > >> On Thu, Sep 20, 2018 at 8:28 PM Richard AG5M via chirp_users >> <chirp_users(a)intrepid.danplanet.com >> <mailto:chirp_users@intrepid.danplanet.com>> wrote: >> >> I have two different Baofeng programming cables.? In Windows Device >> Manager, one shows "Prolific USB to Serial Comm Port", the other shows >> "USB-Serial CH340."? Both work equally well under Windows XP, >> Windows 7, >> and Linux Mint with multiple different Baofeng HTs.? However, only the >> "USB-Serial CH340" works with Windows 10.? What's the difference?? >> Anyone else having this issue?? Any thoughts how to make "Prolific USB >> to Serial Comm Port" work with Windows 10?? I'm really beginning to >> hate >> Windows 10.? Tnx, Richard AG5M >> >> _______________________________________________ > > Miklor website. Get drivers. Install drivers. >

3 2