- Users - lists.chirpmyradio.com

[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

[chirp_users] Baofeng Programming Cables
by Richard AG5M 21 Sep '18

21 Sep '18

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

5 4

[chirp_users] Zastone D9000 programing
by Tony Hunt 20 Sep '18

20 Sep '18

Howdy. Ive just joined this list but have been using Chirp for around 4 years with various radios. How can I get things moving along with the Zastone D9000 radio ? The manufacturer is not very forthcomming with help. I have the Ver 1.0.0.0 software from them but its really frustrating to use and I have now found a painful bug in the software regards reading and programing the receive only memories. No response from them on that problem either. So it would be great to get this one going with Chirp. I have seen requests off the list about this model previously on chirp some years ago but it may have fallen by the wayside. Tell me what help I can provide to get this moving with Chirp. I am all ears . Thanks in advance Tony

1 0

[chirp_users] cloning cable wiring diagram
by Peter 19 Sep '18

19 Sep '18

I recently ordered this TENQ "cloning" cable from Amazon: https://www.amazon.com/gp/product/B00MK02BX2 This cable has Kenwood style connectors (3.5mm TRS & 2.5mm TRS) on each end, for radio-to-radio configuration copy between Baofeng, Wouxun, and "any two-pin style radio with a Kenwood Baofeng plug". I wanted to verify the pinout before adding it to my radio bag. So I spent several hours scouring the Internet for a wiring diagram for such a cable, but with no success. Even simple pinout descriptions were somewhat vague ("back-to-back", etc.). So I ultimately buzzed out the cable with a DVM, tabulated the results, and mocked up a JPEG diagram based on an image that originally came from Miklor.com. See attached for the finished product. The diagram shows that the cable basically has Data Tx from one end connected to Data Rx on the other and vice-versa, with Data Ground connected between both ends. I wanted to submit this to John for possible inclusion on his site, but I don't see any contact form there. I do know that he posts to this list so here I am... John, if you are interested, feel free to re-post wherever you'd like, maybe here? http://www.miklor.com/COM/UV_Technical.php Cheers! (Peter) P.S. I do understand that this list is for CHIRP issues, hence any cable discussion would normally be limited to "programming" cables, e.g. Kenwood to USB with a suitable integrated controller chip. However, I am thinking that this info might be useful to some folks here regardless.

7 12

Re: [chirp_users] cloning cable wiring diagram
by wcurlew＠juno.com 16 Sep '18

16 Sep '18

Peter - at least you have a cable that you can easily chop up to make a connection to something else. I recently had to make a TNC cable for the baofeng using individual 3.5 and 2.5mm connectors. You can cut your up and get 2 for one! Bill ---------- Original Message ---------- From: Peter <ptlambert(a)sbcglobal.net> To: chirp_users(a)intrepid.danplanet.com Subject: Re: [chirp_users] cloning cable wiring diagram Date: Sun, 16 Sep 2018 12:48:11 -0700 Thanks Jim, that's very useful info. I'd read of some folks having issues even starting a clone on the UV-82HP and now I know why. As to the BF-888s, I'd never heard of anyone trying to use a clone cable, but I was up for the adventure. Guess I will need to find more exciting things to do. :@) So now I have a clone cable that I can't really use, and we have a pinout diagram for same... But at least all this is now in the record for posterity's sake. Cheers! (Peter) On 9/16/2018 9:07 AM, Jim Unroe wrote: > On Sat, Sep 15, 2018 at 4:38 PM, Peter <ptlambert(a)sbcglobal.net> wrote: >> Yes, you would want to clone between radios of the same model and >> firmware, otherwise you will likely have issues on the target radio >> ranging from minor to severe. But cloning between dissimilar radios is >> probably not the only way to mess up a radio. And in any case, I am >> only providing the pinout on this particular cable. >> >> I have a few Baofeng UV-82HP radios, and a gaggle of 888s >> walkie-talkies. When I finally get around to attempting clones (between >> the same models, of course), I will post an update with any unfavorable >> outcome here. > You won't be able to use this cable on a UV-82HP or a BF-888s. Modern > Baofeng radios no longer have the radio-to-radio cloning ability. Back > when the N5R/N82 type of firmware was released for UV-5R/UV82 style > radios, the memory layout was changed> Baofeng removed the > radio-to-radio cloning feature to prevent cloning between incompatible > radios. That's also why the covering radio-to-radio cloning was > removed from the miklor.com website. > > The BF-888s never had the radio-to-radio cloning ability. > > To use that cable you will need a Baofeng model with an LCD display > manufactured before the end of 2014 that when powered up with the > [MONI] key pressed displays "COPING" or "COPYING". > > Jim KC9HI > _______________________________________________ > 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 Bill Curlew at wcurlew(a)juno.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com ____________________________________________________________ The 5G Story Nobody Is Telling You The Crux http://thirdpartyoffers.juno.com/TGL3131/5b9ecbd380a5c4bd24806st01vuc

1 0