- Users - lists.chirpmyradio.com

Re: [chirp_users] baofeng cable
by Tom TA 21 Feb '16

21 Feb '16

Greetings, Thanks Jim! Had I noticed the Miklor procedure I probably would have given it a spin. The Miklor procedure offers the advantage of providing a view of all the installed relevant drivers available on the system for a given device. However I do find blazing my own trail sometimes helps me gain a better understanding. This has been a learning process for me as I didn't know until now that there may be multiple driver versions stored on the system for a given USB device. I had the wrong impression that the installation of a new driver overwrote and deleted any older versions. It is nice to know that one can roll back to an older version should a new release have issues. But the deletion of the unwanted drivers offers the convenience of ensuring the desired driver is loaded automatically circumventing the need to make a driver selection on each occasion. It will be interesting to see if the automatic selection of the 3.2.0.0 driver will stick on my system. Having the most recent Prolific driver installed along with the older counterfeit chip friendly version also seems like a good compromise. Presumably the most recent version drivers offer performance advantages thus should be used with genuine Prolific chip devices. It is nice that the port properties driver roll-back feature is easy to access to get back to the 3.2.0.0 driver when needed. I suspect in time with Windows Updates the most recent version will again automatically re-appear on my system. 73 Tom VA7TA --------------------------------------------------------------- You are making this way harder than it needs to be. You don't need to uninstall any drivers. It is better to leave the latest driver installed. If it stays installed, there in no need for Windows to download it. What you do is download, install and then choose the v3.2.0.0 driver. The miklor.com website has a guide for doing this. See steps 6 though 11. http://www.miklor.com/COM/UV_Drivers.php As you can see from the attached picture, I have 4 Prolific device drivers installed. I can switch between any of them at will by using Device Manager. By choosing the v3.2.0.0 driver I can use every Prolific based programming cable that I have (genuine chip or not). By choosing any of the newer drivers, I can determine if the Prolific chip is genuine or not (if it stops working, it isn't genuine). Jim KC9HI

1 0

[chirp_users] Baofeng UV-5R not working
by Lone Wolf 21 Feb '16

21 Feb '16

I have a programmed my uv-5r but for some reason I'm not receiving anything. I have tried several times to program it but it don't seem to pick up any calls from anything. I get all my info for the radio from radio reference and the frequencies. When I get toned out and fire radio goes off my uv-5r just sits there and does nothing. Any ideas on what I might be doing wrong?

6 5

Re: [chirp_users] baofeng cable
by Tom TA 20 Feb '16

20 Feb '16

Greetings All, I wish to thank all those that have been contributing to this thread - I have found it quite helpful! I happen to own two programming cables, one from Baofeng with the Prolific counterfeit chip and one after market cable with a genuine Prolific chip. I have computers running both Windows 10 and Linux Mint 17 with a Chirp installation on both. At the onset I found the Baofeng cable would run OK under Linux but not under Win 10. My low cost after market cable with the genuine Prolific chip worked with both computers. Under Windows 10 I tested the cable by watching Device Manager for the Prolific port error, which was always error 10. Using Device Manager I found the Win 10 driver to be recent version 3.6.787.35x. I found I needed to take the following steps to get the Baofeng cable to work under Windows 10: 1 - Using Device Manager I uninstalled the 3.6.787.x driver and did the recommended 3.2.0.0 install. 2 - I re-tested and discovered the Baofeng cable still did not work with the same error message reported in Device Manager. 3 - I found the driver version being used was still the recent 3.6.787.35x driver which I presumed must have automatically re-loaded from the Internet. 4 - I disabled the Internet and again uninstalled the driver. 5 - I re-tested and discovered the Baofeng cable still did not work with the same error message reported in Device Manager and found that it was now using a slightly older 3.6.x.x driver which I subsequently uninstalled. 6 - I repeated the step 5 test and uninstall procedure several times whilst noting the driver version was becoming older and older. 7 - Finally I got down to version 3.2.0.0 and found the Baofeng cable now worked. 8 - I re-enabled the Internet and did another test and found it still worked. I presume I had a stack of older Prolific drivers stored on disk which remained after routine updates during the previous years of running Windows 7. Apparently the upgrade to Windows 10 did not delete the older drivers (which is probably wise). It appears Windows 10 selects and loads the most recent driver as it took several cycles of deleting before I got down to 3.2.0.0. I noticed once I got there the Roll Back button became greyed out which I guess indicates there are no drivers older than 3.2.0.0 stored on my computer. The moral of the story is to check the version number of the driver under Device Manager>Prolific Port>Properties>Driver and make sure your using version 3.2.0.0 and if not do what ever is necessary to get there. And there is more to this story - when I re-started my computer it reverted the driver back to version 3.6.787.357. I found I had to go to Device Manager and roll back the driver to get back to 3.2.0.0. After doing that once it seemed to stick as it re-loaded 3.2.0.0 the next time I re-started. It remains to be seen how long it will stick. Unless the driver update is blocked by a roll back flag it may again become updated with Windows Update in the future. If so I will need to roll back to 3.2.0.0 again, which I now find is quite easy to do now that I know how. I hope this information is helpful! The driver update and selection features of Windows 10 may be adding confusion to this Baofeng cable, counterfeit Prolific chip driver issue. 73 Tom VA7TA

4 3

Re: [chirp_users] baofeng cable
by Lreiher 20 Feb '16

20 Feb '16

folks, thank you all for your efforts to help me out. the reality is that BENTON seems to have it correct. the cable i purchased was directly from baofeng. i believe that the source was china b/c when i wrote them they told me i bought it 14 mo.s ago and that it was listed as 'works w/ win vista, win7, win 8' and was never listed as for win 10. i pointed out that win 10 did not exist when i bought the cable! clearly, they have used a CLONE of the ftdi chip and, as benton noted, the drivers which FTDI loaded into my PC w/o my knowledge or permission was designed to send TRASH to my cable and render it inoperable! i proved that by using a friend's cable and it worked fine w/ my UV-5RTP; but, my cable on HIS pc is useless. the device mgr sees the cable but does NOT get thru it to see the radio. i asked baofeng if tthey would write code to FIX the cable since it is their shared fault for using a clone in the first place. they didnt respond to that message. now, i have reviewed about 15 programming cables; all - EXCEPT one - are less than $6; oNE is $20 and it is marked 'genuine FTDI cable'. so, i kknow that i could resolve this for 20 bucks. but i am pissed that FTDI trashed something i purchasedd in good faith FROM the manufacturer!! so, i was hoping someone had the expertise to write code to send to my cable to make it functional again. thanks again to you all for your input; however, i'm afraid that i'm still out in left field............. peace, larry KD9AVZ

5 4

[chirp_users] ft-857d clone errors
by GIBBS JON 20 Feb '16

20 Feb '16

I am trying to read from my Yaesu 857d but after a few seconds it just says error. I have tried it on 2 different PCs but could it be the cable?

2 2

[chirp_users] Tecnology net 21/02/16
by ea8ee 20 Feb '16

20 Feb '16

NET TECHNOLOGY This coming Sunday, February 21 at 15h utc Topic: Program control radio equipment CHIRP Part Lecturer: Pavel CO7WP Milanes format: 'Welcome to the stations present -Presentation Of the issue - Questions and answers -Closing systems: - ECHOLINK EA8SPAIN Conference Enviado con MailTrack <https://mailtrack.io/install?source=signature&lang=es&referral=ea8ee1@gmail…> [image: logo] *Jose Manuel Martinez* *EA8EE* Whatsapp: +34692112495 | Telegram :@ea8ee | +967961389 <fax:+967961389> | ea8ee(a)me.com | http://www.radioclubfaycanes.es | Skype: ea8ee1 <#> | ED8ZAB-R XRF007B | http://brandmeister.pd0zry.ampr.org/lh/ <http://plus.google.com/ea8ee1> <http://www.facebook.com/groups/dstar.spain/> <http://www.facebook.com/groups/BrandmeisterDMR/> Radionoticias La Voz de la Libertad, la historia de La Pirenaica <http://feedproxy.google.com/~r/Radio-Noticias/~3/y6LL4P47uiI/la-voz-de-la-l…> Latest Tweet: <https://twitter.com/ea8ee> new BM DMR Spain website https://t.co/wmZkmIbmla #Brandmeister <https://twitter.com/Brandmeister> #Dmr <https://twitter.com/Dmr> Read More <https://twitter.com/ea8ee/statuses/687303036457336833> <https://twitter.com/ea8ee> Get a signature like this: Click here! <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW…>

2 3

Re: [chirp_users] PL Send and receive
by James Pratt Jr. 20 Feb '16

20 Feb '16

Thanks Jim I did the research and found out what I needed to do but I always appreciate help from a fellow ham Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone -------- Original message -------- From: Jim Unroe <rock.unroe(a)gmail.com> Date: 02/20/2016 06:24 (GMT-07:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] PL Send and receive On Fri, Feb 19, 2016 at 9:20 PM, James Pratt <no8rf(a)cox.net> wrote: > How do I set up PL’s in my radio for both send and receive, I what the same > PL for send and receive on simplex freq 465.xxxx I can do this in my > Motorola JT1000 why not in your chrip or am I missing something. > > > > James Hi James, The first thing that you should do is to click View and make sure that "Hide unused fields" is enabled (it should be the default). Now for all channels where you want the same TX and RX CTCSS tone do this... Tone Mode = TSQL ToneSql = {the CTCSS tone frequency} If you want to learn what the CHIRP columns are and how they affect one another, take a look at the guides linked to in section 6 of the CHIRP page on the miklor.com website. http://www.miklor.com/COM/UV_CHIRP.php#guides 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 James at no8rf(a)cox.net To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] PL Send and receive
by James Pratt 20 Feb '16

20 Feb '16

How do I set up PL's in my radio for both send and receive, I what the same PL for send and receive on simplex freq 465.xxxx I can do this in my Motorola JT1000 why not in your chrip or am I missing something. James --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

4 4

[chirp_users] baofeng cable
by Lreiher 18 Feb '16

18 Feb '16

is there any chance that someone is able to write the s/w necessary to [in WIN 10] DELETE the FTDI driver which renders the baofeng cable inoperative AND write the s/w which would REenable the baofeng cable after FTDI has trashed it so we can use it w/ CHIRP and WIN 10? tnx, larry KD9AVZ

9 11

[chirp_users] Chirp and Icom IC-7200
by Bill 17 Feb '16

17 Feb '16

Ok so I am wanting to use chirp to upload memories to my Icom IC-7200 Amateur Radio. Now the IC-7200 has a USB and a CIV connection. My understanding is that the USB should work, But I cannot seem to get it to work. I do not have a CIV cable. So does anyone have any experience with the IC-7200? Can I use the USB connection to upload memories? Or am I going to need a CIV cable? Thanks Bill

7 15