- Users - lists.chirpmyradio.com

[chirp_users] Error after updating to new firmware of Yaesu FT1D and mcOS 10.13.3
by Jeff Zarge - K3JRZ 10 Feb '18

10 Feb '18

Hello. I just updated my Yaesu FT1D to Main 3.01 and DSP 4.15 (both from 09/08/2017). I'm running a 2017 iMac (High Sierra 10.13.3). The firmware & DSP updates went fine on my Windows laptop. Now, I have normally used my iMac (previous was a early 2009 iMac running various OS X versions) and the daily builds of Chirp to program my FT1D (I use the SCU-19 cable that came with my radio). Never had an issue. After doing the two updates and running the latest version of Chirp (currently 20180210) I get the following error when I try to upload my memories back to the radio: "*failed to communications with the radio: radio did not ack block 1*". I have no problem downloading from the radio (although it's a blank list since I reset the radio). I've installed the newest FTDI drivers and and the Python files and still nothing (again, I use the SCU-19 cable that came with my radio - not sure what drivers I really need). Even tried each USB port on my iMac. I'll attach the debug log if that's any help. I'm not a programmer, but I can look through logs and code (do that at work), but I don't see anything that says "HEY! THIS IS THE ISSUE RIGHT HERE!". Maybe someone here will know what to look for? The last time I edited my programming file was in December. I do not remember if I had used Chirp since moving to High Sierra, but I was keeping mostly up-to-date with the daily releases for the Mac. I did go back in through the archives and see someone had issues with 10.13.1, but when he updated to 10.31.2 it was fixed. Well, I'm on 10.13.3. Hrmmm... Did anyone else have this or similar issue? Thanks & 73, Jeff K3JRZ https://www.qrz.com/db/K3JRZ 100WAAW <http://100wattsandawire.com/thegathering/> #404

1 0

[chirp_users] New Daily Build
by Build System 10 Feb '18

10 Feb '18

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-20180210 A list of the changes included in this build (since the last daily) follows: Changes for Build #515 [Dan Smith <dsmith(a)danplanet.com>] Fix MURS1 radio to use validate_memory() and make edges test case tolerant This fixes one test case that should ignore memories that don't validate from the radio, and makes the MURS1 radio support said validation. This is related to #5255 [Jim Unroe <rock.unroe(a)gmail.com>] [MURS-V1] Add Support for BTech MURS-V1 This patch adds support for the BTech MURS-V1 handheld radio. #5255 [Jim Unroe <rock.unroe(a)gmail.com>] [MURS-V1] Prepare CHIRP for BTech MURS-V1 (update baofeng_common.py) The BTech GMRS-V1 and BTech MURS-V1 are very different radios but both respond to the same "magic". This patch provides checks to make sure... 1. the model selected by the user matches the physical radio model. 2. the image being uploaded matches the physical radio model. related to #5255

1 0

[chirp_users] New Daily Build
by Build System 04 Feb '18

04 Feb '18

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-20180204 A list of the changes included in this build (since the last daily) follows: Changes for Build #514 [Rhett Robinson <rrhett(a)gmail.com>] Fix older Icom radio models by properly sending commands with raw encoding. Fixes #5545.

1 0

[chirp_users] VFO
by K Lavinder 01 Feb '18

01 Feb '18

OK, I'm like Phil on Dusk Dynasty; "A low tech man in a high tech world".On a UV5R, how do I go about swapping the VFO limits so that the VFO is disabled?

3 2

[chirp_users] Which radio?
by Chuck Hast 01 Feb '18

01 Feb '18

I see all of the issues with these radio, I want to get something that will do the job, I want at least 2m and 70cm. But would be even better to have something tri-band. So with all of what I have seen, which of these radios do you guys recommend. Chirp does a great job with my Icom, but I would like to get something that I can use and if something happens it is not my Icom handheld. Something that if it falls into the water, or gets whacked I am not out a lot. So what do you guys recommend? -- Chirp + Editcp + MD380Tools on Linux Celestial!!! Chuck -- KP4DJT

17 25

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 26
by C.S. Arthur 31 Jan '18

31 Jan '18

Chuck Hast: BTECH UV-5X3 5 Watt Tri-Band Radio: 130-179.99mhz (VHF), 220-225.99mhz (1.25M), 400-520.99mhz (UHF) Amateur (Ham) <https://www.amazon.com/gp/slredirect/picassoRedirect.html/ref=pa_sp_btf_aps…> $59.00 on amazon prime if you need tri-band

1 0

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 26
by C.S. Arthur 31 Jan '18

31 Jan '18

on the BaoFengs: menu 21 MDF-A and menu 22 MDF-B let you select channel number, channel label/name or frequency. stay away from the VFO/Channel button and it will always show your labels. Channel names have to be assigned in programming software; can’t be done from the key pad. I solved the driver problem by getting the official $12 programming cable from BaoTech…worked perfectly the first time out…then you don’t have to hassle with the drivers (i should say, worked fine on my HP laptop, Win10) 3s christopher arthur KD7EFS Casper, wonderful Wyoming

1 0

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 26
by C.S. Arthur 30 Jan '18

30 Jan '18

to upload to the F9, or the UV-5 for that matter, you need to do two things….set up your frequency plan, labels, etc in CHIRP, and save it. next, copy the contents of the radio to a new chirp database. delete everything in it, and copy from your original chirp freq plan to the now blank one from the receiver. If you go to the Radio pull down, the ‘upload to radio’ will be grayed out unless you are actually in the radio’s database. If you try to upload directly from the CHIRP list that you made, it won’t work but if you select the radio’s database and copy into it, it is happy. Once you figure out some of these obscure kinks you’ll find the BaoFeng is pretty simple. good luck christopher arthur KD7EFS Casper, wonderful Wyoming

1 0

[chirp_users] Gt 5 TP
by Al Manchester 30 Jan '18

30 Jan '18

Good morning, I'm wondering if I can program my Baofeng GT5TP with my Chirp. Having problem. Thank you, Al Manchester

4 5

[chirp_users] How do I download the freq's from the 0-999 chart to my BaoGeng BF-F9V2+
by Harold Witte 30 Jan '18

30 Jan '18

Sent from Yahoo Mail on Android

3 2

[chirp_users] Baofeng UV5R
by K Lavinder 30 Jan '18

30 Jan '18

On a Beofeng UV5R, is there any way to disable the VFO from being displayed so that only channels will be displayed?

3 2

Re: [chirp_users] Leixon 898
by Harrison Cooper 29 Jan '18

29 Jan '18

Changing the subject to something else, rather than responding to the other thread Yes, I've been able to program the 898, but I used a combination of CHIRP and the factory software to get things setup as I wanted. So between the two of those packages, you should be able to obtain what you need. I do not like the 898 that well, for the audio quality from the speaker, its seems to be more on the low side of frequency response. However I do like the scan mode, so I repurposed it to be a VHF/UHF PS scanner, leaving my trucking to handle the 800MHz.

1 0

[chirp_users] [OT] Re: Problems with Norton etc.
by Dave B 29 Jan '18

29 Jan '18

Quite honestly, I'm amazed anyone still thinks running Norton AV is an acceptable solution to a perceived problem. It itself is riddled with inconsistencies and other funnies, plus has a hair trigger for false positives. "Not seen by many users" is NOT a good metric to judge if something is bad or not. Windows own Windows Defender, in conjunction with whatever "Security Essentials" is now called is more than adequate for 90+% of users, and the price is right. Coupled with the use of "uBlock Origin" in your web browsers, to block the obnoxious nasties in on-line add's, and you'll have a slick fast and more than safe enough system. (Heck, that is even in the MS app store now, as well as Chrome's webstore.) The single best AV tool, is common sense... Never, and I mean NEVER *NEVER* Click on a popup you didn't expect*, or go to a site or download something *YOU DID NOT YOURSELF ASK OR GO LOOKING FOR*! And Never EVER respond to anything in unsolicited (spam) email's, however attractive the proposition may look. (* Not even any 'X' close button, that only confirms that they've found a human, and may not even remove the popup. Back out of that website/restart the browser and find another with what you want.) Norton AV used to be good, it's now just more bloat-ware, with questionable practices, and not in truth a particularly good user experience. As above, the best AV tool, is the wet stuff between your ears. As in all life, if something appears to be too good to be true, it probably is bad for you, your PC, and/or your bank account! 73. Dave G0WBX.

11 16

[chirp_users] chirp and screen reader accessibility
by Ray T. Mahorney 27 Jan '18

27 Jan '18

Just a thought here but I wonder if the developers have given consideration to building screen reader accessibility in to the program? Presently, Chirp does not work well if at all with any of the commonly and widely used text to speech screen reading programs such as JAWS and NVDA. The NVDA screen reader is an open source program so its developers may be more receptive to working to build accessibility into Chirp. This question may have come up before and if it has, I apologize in advance. http://www.nvda-project.org Ray T. Mahorney WA4WGA

4 3

[chirp_users] Using The Accessible USB Image For Chirp With Orca Screenreader
by Glenn At Home 27 Jan '18

27 Jan '18

I found the link, but the instructions sound more difficult than it needs to be. I would use the universal USB installer that I'll give a link to, and select the Linux distro of Zorin. The information page on this is: http://www.hamradioandvision.com/chirpvi-liveusb-for-blind-hams/ The Universal USB installer is: https://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ I think that if the image you will download is an ISO image, I don't know why you cannot burn it to a CD, if it is small enough for a CD. However, I think the easiest way to do it is to use the Universal USB installer to download Ubuntu Mate at: https://ubuntu-mate.org/download/ After burning that to DVD or putting it on USB, boot to it and do the following: control S for screenreader On some versions, it's alt + windows S to call up Orca the screenreader. Otherwise, the Linux run command is: alt + F2-key. Then type in: orca and press enter. When Orca is talking: You tab around like you do in windows. You get to the desktop with alt + shift + D The start menu in Ubuntu is alt + F1-key. You arrow around like in Windows. Windows has a DOS shell as it is sometimes called, and we look for command prompt in Windows. Linux has the same thing, called "Terminal". One way we can get there is with alt + control + T. If you like DOS, you will like that. If you get that far, I or others can give you commands for installing Chirp. HTH. Glenn

1 0

[chirp_users] Old XP
by JD Morrow 27 Jan '18

27 Jan '18

Gentlemen, I have an older, pristine, XP machine, that I’m attempting to install CHIRP onto. I’m not a software expert by any imagination. I’m getting the error message: C:\Program Files\Chirp\chirpw.exe This application has failed to start because the application configuration is incorrect. Reinstall... which I have several times. XP version 2002 with SP2 I have purposely kept, and still want to keep the machine, off line. What have I done wrong with the install? Went through wiki and messages, but nothing jumps out. Thank you, John

6 11

[chirp_users] TYT UV8000D
by Schneider Mihály 27 Jan '18

27 Jan '18

Please insert the TYT UV 8000D TRX to the supported radio list. The factory software use dat format. Thanks a lot your effort. Üdvözlettel/With best regards: MEGLEPETÉS Vagyonvédelmi és Szolgáltató Bt. 2071 Páty, Május 1. utca 34. HUNGARY tel/fax:+36 23 452 330; mobil:+36 30 9328 661 <http://meglepetesbt.hu/> http://meglepetesbt.hu/ Figyelem! Jelen üzenet bizalmas információkat, üzleti titkokat és személyes adatokat tartalmazhat, s azt kizárólag annak címzettje ismerheti meg. Az üzenet illetéktelen megismerése, továbbítása, tárolása vagy az azzal végzett bármely más művelet szigorúan tilos és azt a törvény bünteti. Ha jelen üzenetet Ön tévedésből kapta, kérjük, értesítse a feladót e-mailen vagy egyéb módon (MEGLEPETÉS Bt., 2071 Páty, Május 1. utca 34., tel.: +36-23-452 330), majd törölje a kapott üzenetet. A jelen üzenet küldőjének elektronikus levélcímére való üzenetküldéssel Ön hozzájárul ahhoz, hogy a levél tartalmát az MEGLEPETÉS Bt.-nek a címzetten kívüli kijelölt munkatársa megismerje. P Antes de imprimir, piense en el Medio Ambiente. Before printing think about the Environment. Avant d'imprimer, pensez à l'Environnement.P

1 0

Re: [chirp_users] Baofeng channel labels
by C.S. Arthur 26 Jan '18

26 Jan '18

thanks guys…i thought it would be something simple like that; reading that fine print in the user manual where they describe the menu functions is problematic. maybe it is time for cheaters or something. 3s and 8s chris arthur KD7EFS casper, wyo

1 0

[chirp_users] Problems with Norton etc.
by Tom Simonson 26 Jan '18

26 Jan '18

I ran into the problem of Norton treating Chirp as malware in Feb of 2016. I was using the current program Norton Internet Security on some Windows 7 machines (32 and 64 bit systems). I was able to over-ride the objections of Norton and install the program. At that time, when Norton had problems with a program, it was possible to look at the "details" of the problem - which in this case were partly because the program (or version) was not seen on very many systems, making is suspicious. Within the dialog process of the Norton program, it was possible to report that it might be a false positive. I did this and got the all-clear from Norton a few days later. My recollection is hazy, but I think that I had to provide a download link to the program in question (Chirp installer). Below is the response that I got from Symantec after evaluating the version of CHIRP. Note that the reference to pro-active whitelisting brings up a page saying that advance whitelisting is no longer an option, with a link to a report false positives page. " In relation to submission [3917013]. Upon further analysis and investigation we have verified your submission and as such this detection will be removed from our products. The updated detection will be distributed in the next set of virus definitions, available via LiveUpdate or from our website at http://securityresponse.symantec.com/avcenter/defs.download.html Please note that whitelisting can take up to 24 hours to take effect. Decisions made by Symantec are subject to change if alterations to the Software are made over time or as classification criteria and/or the policy employed by Symantec changes over time to address the evolving landscape. If you are a software vendor and would like to upload your software for proactive whitelisting, please complete the following form: https://submit.symantec.com/whitelist For more information on best practices to reduce false positives: http://www.symantec.com/content/en/us/enterprise/white_papers/b-to_increase… " -- Tom Simonson, Alameda CA (tom(a)tsimonson.com)

1 0

[chirp_users] update on the Lexien 898S won't program
by Alan Wilson 26 Jan '18

26 Jan '18

The drivers are the older version (which should work). I read in the archives something about deleting chrip and data files, then reinstall read from radio and it works. I'll try that this weekend and see if it works and report back. 73 alan --

1 0

[chirp_users] will not copy channel names to radio
by C.S. Arthur 26 Jan '18

26 Jan '18

at the risk of asking a question that may have been posted earlier (several hours of searching failed to yield results): recently purchased a BF-F9 V2+. the most recent CHIRP daily allows me to program all fields successfully, but the channel name field will not copy to the radio. turning everything off and copying FROM the radio into a new download file shows the channel names are in there somewhere, but they do not show up on the radio display. Any ideas? Thanx christopher arthur KD7EFS … a baofeng BF-F9V2+ and a UV-5RTP (channel names work properly with the UV-5)

3 2

[chirp_users] Norton Won't Allow Newest Daily Build to Load
by alpha272003＠aol.com 26 Jan '18

26 Jan '18

My Norton antivirus tells me: "chirp-daily-20180123-installer.exe is not safe and has been removed." I tried forcing with "download anyway", or "run anyway" and it still won't allow the newest download. Using Windows 7, and last successful download of a daily build was 20171229. Any suggestions? Bill W3OWL

6 6

[chirp_users] FTDI cable for Yaesu FT-60 using Mac OS
by T.E. Klamberg Klamberg 24 Jan '18

24 Jan '18

The struggle continues…. I downloaded the driver from FTDI website and went through installation. Np problems there. I then went to the System Report page to see if the driver appeared on the USB list of drivers. Nothing shows that would tell me that a FTDI driver was installed anywhere. I suspect the com/USB port is not communicating with the download, or the cable is not communicating. At this point, I am lost as to what to do next. I hope I have provided enough info for your collective assistance. Thanks. Tip Klamberg N9MVX

2 1

[chirp_users] Problem with Lexien 898S
by Alan Wilson 24 Jan '18

24 Jan '18

Hi, I got an 898S early last year. It did come with a programming cable but I ordered one off of ebay. I received it, plugged it in and it worked. Next time I tried it I had to plug it in a couple of times before it would recognize it (I did get it to work). Fast forward to Dec I've plugged in numerous time and will not recognize radio. Obviously its either cable or maybe in the radio. How to I tell which? without buying a new cable. 73 Alan --

4 5

[chirp_users] Valley Ent. cable and mac OS High Sierra
by T.E. Klamberg Klamberg 23 Jan '18

23 Jan '18

The last problem I had is overcome, that being selecting the Yaesu FT-60 from the dropdown menu. Chirp is a little picky how you select items, but I found it. Now has to do with the cloning. When I plug in the Valley Enterprise FTDI cable, red and green lamps on the USB plug flash once simultaneously; very fast and only once. I set up the radio to clone without issue. When I set up Chirp to download from the radio, the port selection is only one: /dev/cu.bluetooth-incoming-port. When I press the PTT button on the radio, I get RX, then an error on Chirp. When I remove the USB from the MacBook Pro, there are no red/green lamp flash at all. When it comes to using Terminal on mac, I am really concerned that I may screw something up beyond all recognition. I did download the the FTDI driver but to no avail. I really appreciate any help y’all can provide on this issue. Thanks. Tip Klamberg N9MVX Mascoutah, IL

2 1

[chirp_users] Mac and cloning cables
by Michael Sanford 23 Jan '18

23 Jan '18

I have used RT System USB cables for my Mac to operate my FT 920 using MLDX with great success. I have asked RT Systems, (who make a plethora of USB/RS 232 cables for just about every radio on earth) if they plan to write driver software for their cloning cables for HT’s and VHF/UHF radios. They assure me that they are working on the problem. If anyone needs a Mac driver for RT Systems’ USB/RS232 cables, you can contact me, I have the link or put a question into their support network. Mike K0CCP

1 0

[chirp_users] leixon 898S v/u radio duel banks v108
by Neil B 23 Jan '18

23 Jan '18

just wondering if there was any more dev on the leixon 898S v/u radio duel banks mine is 108.(via p3) this below is only way i can use it with chirps superior editing. Open oem sw with last saved file .LX19 and write to radio (VV898S_USER_V107) Open chirp and load module for leixen_107.py from 4069 Read radio into chirp Edit radio mems as required. Upload to radio via chirp. Quit chirp Read radio using oem sw and Save/backup to new file.(.lx19 extenstion) This is only way it works…if I save the read image from chirp to img file, re-opening it is id’ed as Jetstream and then will not upload properly. Unable to change.

2 1

[chirp_users] New Daily Build
by Build System 23 Jan '18

23 Jan '18

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-20180123 A list of the changes included in this build (since the last daily) follows: Changes for Build #513 [Rhett Robinson <rrhett(a)gmail.com>] Update IC-2730 driver to swap which byte is considered DTCS. I sniffed the traffic the official software sends to the radio, and it only changes the second byte, so that seems to be where dtcs is stored. Addresses #2745

1 0

Re: [chirp_users] Valley Enterprise USB and FT-60
by Dave B 22 Jan '18

22 Jan '18

Hi. Sometimes the (long) list of radios falls off the bottom of the screen, you may need to scroll or shift it up to see Yaesu, then select the radio with the other drop-down tool. Yaesu has been in there for a long time, the FT-60 is listed too, and when I try it, it walks me through the procedure needed at the radio, and then waits for a clone download (that never comes, as I don't have a FT-60 connected!) so I cancel and exit. This in "CHIRP daily-20180115" Best get your instance of CHIRP from the website, not relying on OS managed repositories, that are usually somewhat out of date. As you are a Mac user, go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download And follow the instructions there under the MacOS users section. Check also:- https://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips In particular re application security for your version of OS, and the notes based on whatever chip-set your USB<>serial cable is based on. VE don’t actually tell what chip-set they use, that I could see on the website. Never mind, the OS will tell you, if you check the system message log immediately after connecting the lead to the computer. Under Linux, the easiest way is from a command line terminal, issue a dmesg command, and what you want will be close to the end of the (verbose) listing. Google implies that Mac OS has the same command, so ??? Hope something helps. 73. Dave G0WBX (A Linux, not a Mac user.) On 22/01/18 20:00, T.E. Klamberg wrote: > Message: 1 > Date: Sun, 21 Jan 2018 15:37:54 -0600 > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> > Subject: [chirp_users] Valley Enterprise USB and FT-60 > To: chirp_users <chirp_users(a)intrepid.danplanet.com> > Message-ID: <DB9604EF-3AFA-4319-9E34-2F1BC4AD37B8(a)yahoo.com> > Content-Type: text/plain; charset=us-ascii > > Hi All, > > I received my cable from Valley Ent. Oh Boy, here I go. Gonna make that radio tune like never before. I insert the cable into the radios, and put the radio in Clone mode as per instructions. Plug in the USB into my MacBook Pro, then I go to the <Download from Radio> on the Radio menu bar on the Chirp app. > Surprise!! > No Yaesu listed at all. List starts at Alinco and ends with three or four radios starting with W. > No, I repeat, no Yaesu. > Yaesu is listed as supported on the Chirp website, so I am full-gonzo confused. > Can anyone enlighten me and provide some help, please? > > Tip, N9MVX > > ------------------------------ >

1 0

[chirp_users] Valley Enterprise USB and FT-60
by T.E. Klamberg Klamberg 22 Jan '18

22 Jan '18

Hi All, I received my cable from Valley Ent. Oh Boy, here I go. Gonna make that radio tune like never before. I insert the cable into the radios, and put the radio in Clone mode as per instructions. Plug in the USB into my MacBook Pro, then I go to the <Download from Radio> on the Radio menu bar on the Chirp app. Surprise!! No Yaesu listed at all. List starts at Alinco and ends with three or four radios starting with W. No, I repeat, no Yaesu. Yaesu is listed as supported on the Chirp website, so I am full-gonzo confused. Can anyone enlighten me and provide some help, please? Tip, N9MVX

5 6

Re: [chirp_users] Baofeng UV 82X
by Dave 17 Jan '18

17 Jan '18

I used factory software to configure as a 2/220 radio it was showing 2/440. I can not save the programing in the factory software or upload the file from the radio it uploads a little and then gives a connection error. Factory will download to radio but once I close the program I get to start over again. Chirp will let me upload the file but, errors out the 220 repeaters but not the 220 simplex frequencies. If I edit and reenter the repeaters I can download the file to the radio and it works but I just opened the saved file on my computer and it has error'd out the repeaters again. Also as I enter frequencies in the radio, 2 meters shows an offset of .600 but by the time I add the offset that has changed to 0.00 same on 220 the offset changes to 0.0 even though I have entered a + or - offset. At least the radio is programmed so, thanks for the help. Dave N7AM On 1/17/2018 1:00 PM, chirp_users-request(a)intrepid.danplanet.com wrote: > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > This is because your radio is telling CHIRP is it a VHF/UHF model. It > was probably configured incorrectly from the factory. I've see it > before. > > You can likely "fix" it using the factory software. Email a freshly > downloaded CHIRP Radio Images (*.img) file to me and I can help you > with it. > > Jim KC9HI > > >

3 2

[chirp_users] Baofeng UV 82X
by Dave 16 Jan '18

16 Jan '18

When I try to download from my 82X it lists the 220 channels as "error" and the 82X is listed as supported on the web page but, not in the list in the program. Any suggestions? N7AM

3 2

[chirp_users] New Daily Build
by Build System 16 Jan '18

16 Jan '18

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-20180115 A list of the changes included in this build (since the last daily) follows: Changes for Build #512 [Rhett Robinson <rrhett(a)gmail.com>] Updates .hgigore a bit. Notably, this includes .tox which otherwise inundates the output of hg status after running tests. Also includes a few other files that end up existing but untracked. #0 [Rhett Robinson <rrhett(a)gmail.com>] Shorten a pydoc line in icf.py to fix tests. #0 [Dan Smith <dsmith(a)danplanet.com>] [ic2730] Add test image for Icom 2730A from Rhett Related to #2745 [Rhett Robinson <rrhett(a)gmail.com>] [ic2730a] Add support for Icom IC-2730A. Fixes #2745. [Rhett Robinson <rrhett(a)gmail.com>] Adds support for a raw-mode Icom driver. This is required for the IC-2730A (part of #2745).

6 5

[chirp_users] Reply to MMcabe
by Peter Ryan 16 Jan '18

16 Jan '18

@mmcabe: I am new also. I ran into the same type problems you are, using a Valley Enterprises cable, a Yaesu FT-60, and a Macbook. I solved it by reloading all 3 software apps again...Chirp, Python and PL2303...those being the software apps needed for my Macbook. Fearing a repeat need for this requirement, I have left my computer running since the software re-installs. But give this approach a try. It did work for me. And make SURE you execute the correct steps in the exact CORRECT ORDER vis-a-vis the computer/radio or you will get the same "errors" displayed that are bothering you now.. Good luck.

3 2

Re: [chirp_users] Reply to MMcabe
by Mike 16 Jan '18

16 Jan '18

Thanks. I will give it a try I spent hours manually programming it > On Jan 15, 2018, at 4:57 PM, Peter Ryan via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: > > @mmcabe: I am new also. I ran into the same type problems you are, using a Valley Enterprises cable, a Yaesu FT-60, and a Macbook. I solved it by reloading all 3 software apps again...Chirp, Python and PL2303...those being the software apps needed for my Macbook. Fearing a repeat need for this requirement, I have left my computer running since the software re-installs. But give this approach a try. It did work for me. And make SURE you execute the correct steps in the exact CORRECT ORDER vis-a-vis the computer/radio or you will get the same "errors" displayed that are bothering you now.. Good luck. > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to mike at mmccabe1(a)telus.net > To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] BF-T1 - Duplex: OFF
by Drew from Zhrodague 15 Jan '18

15 Jan '18

I am really excited to see support for the BF-T1! However, I did notice that I am not able to set the Duplex setting to OFF. I like to listen to the local UHF police frequencies, but prefer to prevent accidental transmissions. I am able to disable transmit with my Baofeng UV-5Rs and with the WLN KD-C1 radios using CHIRP. I am using the deb-based chirp-daily repo under Ubuntu 16. Any ideas, or am I missing something?

3 2

[chirp_users] How to Edit columnb information in chirp csv file?
by ve5rmk＠sasktel.net 13 Jan '18

13 Jan '18

Hi: I am a New user of chirp, I downloaded a repeater file for my area from Repeaterbook. My Radio is a ICOM t70a, I wish to upload this file to my tranceiver. I have the t70a to display repeaters by Name! I can sort the Location names alphabetically in the comments column from A to Z which is what I want, but this randomly sorts the memory locations in the Loc column, eg: 25, 42, 52, 7........ I would like to have the repeaters to be in alpabetical order by location, AND have the memory Locations to be in order from 1to 58 as there is 58 repeaters. I would also like to change entries in the Name column to locations in alphabetical order instead of reapeater callsign as they are now. How would I do this? Any help Greatly appreciated! Rodney Kozey VE5RMK

3 2

[chirp_users] UV-50x2 / CHIRP Questions
by David Mosley 12 Jan '18

12 Jan '18

Hello All, I have a new B-TECH UV-50x2 and I am using CHIRP to program it. I would like to have the display set up as: A: Name (2m band)B: Frequency (for A)C: Name (70cm band)D: Frequency (for B) Is it possible for A to scan 2m only and C to scan 70cm only, or, A&B to scan together and C&D to scan together? If so, what settings to I change in CHIRP to accomplish this? Thanks so much for your help.73'sDavid Mosley, LPOf all the roads you take in life, make sure some are DIRT!!!! Don't retreat, RELOAD!!!! KG5FAC

6 8

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 10
by Dave B 11 Jan '18

11 Jan '18

On 10/01/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Subject: Re: [chirp_users] Concurrance > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > <CAJfKeYDxStkmLEqnoaWB=zUyY7QiJLPZM=c_Y4prqzVho=E4vQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Like my Mother always said, "If you do not have anything nice to say, do > not talk at all". I'm astonished on how bad some forums treat newbees. Yes, > it gets old sometimes answering the same basic question many times, But > giving a rude answer will only keep others from seeking help. Do we want > the hobby to grow. or wither away as we all get old? The only problem there, is if the same lame question is being asked time and time and time again, then there is something seriously missing in the instructions, documentation or help files. More often than not, it's the creators of an application or package, that create that documentation (initially at least) but it's plain as the nose on our faces, that often they are "too close" to it all, to realise that some small but critical detail that is plain and obvious to them, is total smoke and mirrors to other people. As always, the devil is in the detail. In this case, my impression is that the documentation explaining the programming interface lead/hardware is often seriously lacking. Not helped any by the radio manufacturers in some cases, and the plethora of other sites on the inter-web, that often have conflicting information. 73. Dave G0WBX. (Who in the past has been, and will probably again be the noob who's been flamed for asking "dumb" questions. Plus at other times guilty as charged of the curt one liners. We've all done it I suspect. Hopefully I wont any more.)

3 2

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea@arrl.net>
by Mike 11 Jan '18

11 Jan '18

It’s an RT cable. The problem seems to be that Chirp does not know the name of the output on USB. Sent from my iPad > On Jan 9, 2018, at 12:07 AM, Jardy via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: > > If Device Manager shows your cable to be a Prolific cable, roll your driver back to 3.2.0.0. This can be found at www.miklor.com. > > Jardy Dawson WA7JRD > Message sent through sub space hailing frequencies using the Universal Translator. > > >> On Jan 8, 2018, at 20:49, Mike McCabe <mmccabe1(a)telus.net> wrote: >> >> I am new here so please forgive me if I am dealing with my issue improperly >> >> I am trying to program a yeast vx8dr handheld It goes to clone but then gives the message to the effect that the radio is not transferring data >> >> Windows10, USB shows the cable, rebooted computer. Always the same result >> >> Can anybody help? >> >> Mike >> >>> On Jan 8, 2018, at 5:16 PM, Skip <rockyvista(a)windstream.net> wrote: >>> >>> So that is how Hillary did it! >>> >>> From: Christopher F. Beesley >>> Sent: Monday, January 08, 2018 2:03 PM >>> To: chirp_users(a)intrepid.danplanet.com >>> Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea(a)arrl.net> >>> >>> Hi David (and others), >>> I'm using default Windows 10 coding/decoding. It works perfectly with almost everything I use, including Word, Access, Excel, Visio, Audition, Winamp, Firefox, EditPad, Paint, an AMR converter, Bulk Rename, and several Canon utilities to name but a few. It also works perfectly with older versions of several of the above. Emails in both directions via Yahoo! and MSN are no problem. >>> I find incorrect punctuation in a fair number of 'Comments' made about various news items as well as the chirp-users messages. It has been suggested that the incorrect punctuation is because of data mis-handling by systems in other countries where the apostrophe is not recognised in their language and the question-mark is substituted at that point. I like that explanation, it fits in with the world-wide nature of Amateur Radio as well as news-item comments from all over the world. Such activities would be out of the control of both the sender and recipient. >>> This has legal implications - the email that someone sends may not look like the email that is received, and therefore will be useless as evidence. >>> Thanks for yours and everyone else's interest, >>> 73, Chris >>> >>> >>> From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> >>> Sent: 08 January 2018 20:00 >>> To: chirp_users(a)intrepid.danplanet.com >>> Subject: chirp_users Digest, Vol 109, Issue 8 >>> >>> Send chirp_users mailing list submissions to >>> chirp_users(a)intrepid.danplanet.com >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> or, via email, send a message with subject or body 'help' to >>> chirp_users-request(a)intrepid.danplanet.com >>> >>> You can reach the person managing the list at >>> chirp_users-owner(a)intrepid.danplanet.com >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of chirp_users digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: chirp_users Digest, Vol 109, Issue 6 and many others >>> (D.J.J. Ring, Jr.) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Mon, 8 Jan 2018 02:14:17 -0500 >>> From: "D.J.J. Ring, Jr." <n1ea(a)arrl.net> >>> Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and >>> many others >>> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> >>> Message-ID: >>> <CADO5RbiZU9VbjTVB6G-gO3sNn8rMMr2d6j4u1ED05-O-TG_z3w(a)mail.gmail.com> >>> Content-Type: text/plain; charset="utf-8" >>> >>> Chris, >>> >>> Check your language settings? What encoding are you using? >>> >>> I use UTF-8 on my desktop for the locale. If someone sends me a different >>> encoding it often appears as you say it does. >>> >>> I am using an Android at the monent, so I have no idea of tge encoding, but >>> probably UTF-8. >>> >>> 73 >>> >>> David N1EA >>> On Jan 6, 2018 3:16 PM, "Christopher F. Beesley" <chrisbees2(a)hotmail.com> >>> wrote: >>> >>> > Hi, Chris here. What's all this utter nonsense that is becoming more and >>> > more common whereby the question mark is used instead of the apostrophe? >>> > I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m >>> > fed up of seeing stuff that won?t read easily because of it. It?s rubbish! >>> > Where did you lot learn English grammar' >>> > >>> > Chris. N.B. All punctuation errors above are deliberate, designed to >>> > emphasise the point of this message. >>> > >>> > >>> > ------------------------------ >>> > *From:* chirp_users-bounces(a)intrepid.danplanet.com < >>> > chirp_users-bounces(a)intrepid.danplanet.com> on behalf of >>> > chirp_users-request(a)intrepid.danplanet.com <chirp_users-request@intrepid. >>> > danplanet.com> >>> > *Sent:* 06 January 2018 20:00 >>> > *To:* chirp_users(a)intrepid.danplanet.com >>> > *Subject:* chirp_users Digest, Vol 109, Issue 6 >>> > >>> > Send chirp_users mailing list submissions to >>> > chirp_users(a)intrepid.danplanet.com >>> > >>> > To subscribe or unsubscribe via the World Wide Web, visit >>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> > or, via email, send a message with subject or body 'help' to >>> > chirp_users-request(a)intrepid.danplanet.com >>> > >>> > You can reach the person managing the list at >>> > chirp_users-owner(a)intrepid.danplanet.com >>> > >>> > When replying, please edit your Subject line so it is more specific >>> > than "Re: Contents of chirp_users digest..." >>> > >>> > >>> > Today's Topics: >>> > >>> > 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) >>> > 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) >>> > 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) >>> > 4. Re: Fwd: FDTI chip compatibility with Mac >>> > (Nigel A. Gunn G8IFF/W8IFF) >>> > 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) >>> > 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) >>> > 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) >>> > 8. Linux PPA problem? (Tom Consodine ND5Y) >>> > >>> > >>> > ---------------------------------------------------------------------- >>> > >>> > Message: 1 >>> > Date: Fri, 5 Jan 2018 17:31:13 -0600 >>> > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> >>> > Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac >>> > To: chirp_users(a)intrepid.danplanet.com >>> > Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> >>> > Content-Type: text/plain; charset="us-ascii" >>> > >>> > Here is the answer I got from FTDI regarding their cable chipsets! >>> > Let me ask again: how many of you are Mac iOS users, and where did you get >>> > your cloning cables from? >>> > THanks. >>> > Tip N9MVX >>> > >>> > > Begin forwarded message: >>> > > >>> > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> >>> > > Subject: RE: FDTI chip compatibility with Mac >>> > > Date: January 5, 2018 at 16:41:00 CST >>> > > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support < >>> > us.support(a)ftdichip.com> >>> > > >>> > > Tipton: >>> > > >>> > > FTDI does not support iOS. >>> > > >>> > > >>> > > Best Regards, >>> > > >>> > > Cameron Forbes >>> > > Customer Support Engineer >>> > > >>> > > Future Technology Devices International Limited >>> > > 7130 SW Fir Loop >>> > > Tigard, OR 97223-8160 >>> > > Tel: 503.726.5415 >>> > > Fax: 503.547.0987 >>> > > >>> > > >>> > > -----Original Message----- >>> > > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com <n9mvx(a)yahoo.com>] >>> > > Sent: Tuesday, January 02, 2018 8:37 AM >>> > > To: US Support >>> > > Subject: FDTI chip compatibility with Mac >>> > > >>> > > My question has to do with the FTDI chipset and Apple computers. I have >>> > a MacBook Pro with iOS High Sierra version 10.13.2 installed. >>> > > Is your chipset compatible with that iOS? >>> > > Thank you. >>> > > >>> > > Tipton Klamberg >>> > > Mascoutah, Il 62258 >>> > > (618) 670-1502 >>> > > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source= >>> > EmailfooterApril17&utm_medium=EmailfooterApril17&utm_ >>> > campaign=EmailfooterApril17&utm_term=EmailfooterApril17& >>> > utm_content=EmailfooterApril17> >>> > > Registered in Scotland No 136640 >>> > > This message contains confidential information and is intended only for >>> > the individual named. If you are not the named addressee you should not >>> > disseminate, distribute or copy this e-mail. Please notify the sender >>> > immediately by e-mail if you have received this e-mail by mistake and >>> > delete this e-mail from your system. E-mail transmission cannot be >>> > guaranteed to be secure or error-free as information could be intercepted, >>> > lost, destroyed, arrive late or incomplete. The sender therefore does not >>> > accept liability for any errors or omissions in the contents of this >>> > message, which arise as a result of e-mail transmission. Future Technology >>> > Devices International Ltd has taken every reasonable precaution to ensure >>> > that any attachment to this e-mail has been swept for viruses. However, we >>> > cannot accept liability for any damage sustained as a result of software >>> > viruses and would advise that you carry out your own virus checks before >>> > opening any attachment. >>> > >>> >

1 0

[chirp_users] Concurrance
by Al Jones 10 Jan '18

10 Jan '18

I like the give and take from all the people here *except* that there are times when it's not helpful at all. We get a new member who doesn't know what he's doing, thinks he's read everything and is still missing "something" --- and one of our beneficent members replies "RTFM!" or someone else chimes in with "get the right cable!" or better yet "That won't work!" Those one line zingers are not only NO help, they're probably going to turn off some guy who might eventually be the one to help someone else, down the line. I have a friend who had a Linux problem and the response he got here was - "It works fine with *my* Ubuntu!" Sometimes confirmation that something works is a big help, it just means that we're not looking in the right place. When I phrased his question differently I got some great assistance ... there are some good guys here and to them I say "Thanks!" << tripping off my soapbox, sorry >>

5 4

Re: [chirp_users] Concurrance
by Walt Childson 09 Jan '18

09 Jan '18

Hey guys, you are all awesome. Keep up the good work. I'm on my boat in Mexico, and have not been interested in chirp for 7 months. But even though I only get some coverage when I'm in port, I still read most of the threads. I do agree that it might be frustrating with newbe's but answers or links to the answer will help us all. Adios Walt N6STM On Jan 9, 2018 3:32 PM, "Al Jones" <al(a)aljones.us> wrote: I like the give and take from all the people here *except* that there are times when it's not helpful at all. We get a new member who doesn't know what he's doing, thinks he's read everything and is still missing "something" --- and one of our beneficent members replies "RTFM!" or someone else chimes in with "get the right cable!" or better yet "That won't work!" Those one line zingers are not only NO help, they're probably going to turn off some guy who might eventually be the one to help someone else, down the line. I have a friend who had a Linux problem and the response he got here was - "It works fine with *my* Ubuntu!" Sometimes confirmation that something works is a big help, it just means that we're not looking in the right place. When I phrased his question differently I got some great assistance ... there are some good guys here and to them I say "Thanks!" << tripping off my soapbox, sorry >> _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Walt Childson at wchildson(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com

1 0

[chirp_users] Subject lines
by Jardy Dawson 09 Jan '18

09 Jan '18

You mean such as "Please"? Jardy Dawson WA7JRD Ham Radio We keep trying to interfere with elections, but pesky moose and squirrel keep interfering! On Jan 9, 2018, at 10:31, Ted Timmons <ted(a)perljam.net> wrote: Also: use good subject lines. There's no reason you can't state the topic of the message rather than something short or misleading. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72(a)yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

3 2

[chirp_users] Please!
by Chas 09 Jan '18

09 Jan '18

When I joined this list, I expected to find tech- savy individuals working to enhance a great piece of free software. However, I keep getting digests filled with the total previous digest copied multiple times. If you simply clean up your reply, maybe include a relevant quote, and add a meaningful subject - some of us would be inclined to read it and help. - That concludes my vent. Please be brief and don't be lazy. CT No tree, hard or soft, has been harmed by the senfing of this email; but many electrons have been inconvenienced.

3 2

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea@arrl.net>
by Mike McCabe 09 Jan '18

09 Jan '18

I am new here so please forgive me if I am dealing with my issue improperly I am trying to program a yeast vx8dr handheld It goes to clone but then gives the message to the effect that the radio is not transferring data Windows10, USB shows the cable, rebooted computer. Always the same result Can anybody help? Mike > On Jan 8, 2018, at 5:16 PM, Skip <rockyvista(a)windstream.net> wrote: > > So that is how Hillary did it! > > From: Christopher F. Beesley > Sent: Monday, January 08, 2018 2:03 PM > To: chirp_users(a)intrepid.danplanet.com > Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea(a)arrl.net> > > Hi David (and others), > I'm using default Windows 10 coding/decoding. It works perfectly with almost everything I use, including Word, Access, Excel, Visio, Audition, Winamp, Firefox, EditPad, Paint, an AMR converter, Bulk Rename, and several Canon utilities to name but a few. It also works perfectly with older versions of several of the above. Emails in both directions via Yahoo! and MSN are no problem. > I find incorrect punctuation in a fair number of 'Comments' made about various news items as well as the chirp-users messages. It has been suggested that the incorrect punctuation is because of data mis-handling by systems in other countries where the apostrophe is not recognised in their language and the question-mark is substituted at that point. I like that explanation, it fits in with the world-wide nature of Amateur Radio as well as news-item comments from all over the world. Such activities would be out of the control of both the sender and recipient. > This has legal implications - the email that someone sends may not look like the email that is received, and therefore will be useless as evidence. > Thanks for yours and everyone else's interest, > 73, Chris > > > From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> > Sent: 08 January 2018 20:00 > To: chirp_users(a)intrepid.danplanet.com > Subject: chirp_users Digest, Vol 109, Issue 8 > > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. Re: chirp_users Digest, Vol 109, Issue 6 and many others > (D.J.J. Ring, Jr.) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 8 Jan 2018 02:14:17 -0500 > From: "D.J.J. Ring, Jr." <n1ea(a)arrl.net> > Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and > many others > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > <CADO5RbiZU9VbjTVB6G-gO3sNn8rMMr2d6j4u1ED05-O-TG_z3w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Chris, > > Check your language settings? What encoding are you using? > > I use UTF-8 on my desktop for the locale. If someone sends me a different > encoding it often appears as you say it does. > > I am using an Android at the monent, so I have no idea of tge encoding, but > probably UTF-8. > > 73 > > David N1EA > On Jan 6, 2018 3:16 PM, "Christopher F. Beesley" <chrisbees2(a)hotmail.com> > wrote: > > > Hi, Chris here. What's all this utter nonsense that is becoming more and > > more common whereby the question mark is used instead of the apostrophe? > > I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m > > fed up of seeing stuff that won?t read easily because of it. It?s rubbish! > > Where did you lot learn English grammar' > > > > Chris. N.B. All punctuation errors above are deliberate, designed to > > emphasise the point of this message. > > > > > > ------------------------------ > > *From:* chirp_users-bounces(a)intrepid.danplanet.com < > > chirp_users-bounces(a)intrepid.danplanet.com> on behalf of > > chirp_users-request(a)intrepid.danplanet.com <chirp_users-request@intrepid. > > danplanet.com> > > *Sent:* 06 January 2018 20:00 > > *To:* chirp_users(a)intrepid.danplanet.com > > *Subject:* chirp_users Digest, Vol 109, Issue 6 > > > > Send chirp_users mailing list submissions to > > chirp_users(a)intrepid.danplanet.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > or, via email, send a message with subject or body 'help' to > > chirp_users-request(a)intrepid.danplanet.com > > > > You can reach the person managing the list at > > chirp_users-owner(a)intrepid.danplanet.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of chirp_users digest..." > > > > > > Today's Topics: > > > > 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > > 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) > > 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) > > 4. Re: Fwd: FDTI chip compatibility with Mac > > (Nigel A. Gunn G8IFF/W8IFF) > > 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) > > 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > > 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) > > 8. Linux PPA problem? (Tom Consodine ND5Y) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 5 Jan 2018 17:31:13 -0600 > > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> > > Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac > > To: chirp_users(a)intrepid.danplanet.com > > Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> > > Content-Type: text/plain; charset="us-ascii" > > > > Here is the answer I got from FTDI regarding their cable chipsets! > > Let me ask again: how many of you are Mac iOS users, and where did you get > > your cloning cables from? > > THanks. > > Tip N9MVX > > > > > Begin forwarded message: > > > > > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > > > Subject: RE: FDTI chip compatibility with Mac > > > Date: January 5, 2018 at 16:41:00 CST > > > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support < > > us.support(a)ftdichip.com> > > > > > > Tipton: > > > > > > FTDI does not support iOS. > > > > > > > > > Best Regards, > > > > > > Cameron Forbes > > > Customer Support Engineer > > > > > > Future Technology Devices International Limited > > > 7130 SW Fir Loop > > > Tigard, OR 97223-8160 > > > Tel: 503.726.5415 > > > Fax: 503.547.0987 > > > > > > > > > -----Original Message----- > > > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com <n9mvx(a)yahoo.com>] > > > Sent: Tuesday, January 02, 2018 8:37 AM > > > To: US Support > > > Subject: FDTI chip compatibility with Mac > > > > > > My question has to do with the FTDI chipset and Apple computers. I have > > a MacBook Pro with iOS High Sierra version 10.13.2 installed. > > > Is your chipset compatible with that iOS? > > > Thank you. > > > > > > Tipton Klamberg > > > Mascoutah, Il 62258 > > > (618) 670-1502 > > > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source= > > EmailfooterApril17&utm_medium=EmailfooterApril17&utm_ > > campaign=EmailfooterApril17&utm_term=EmailfooterApril17& > > utm_content=EmailfooterApril17> > > > Registered in Scotland No 136640 > > > This message contains confidential information and is intended only for > > the individual named. If you are not the named addressee you should not > > disseminate, distribute or copy this e-mail. Please notify the sender > > immediately by e-mail if you have received this e-mail by mistake and > > delete this e-mail from your system. E-mail transmission cannot be > > guaranteed to be secure or error-free as information could be intercepted, > > lost, destroyed, arrive late or incomplete. The sender therefore does not > > accept liability for any errors or omissions in the contents of this > > message, which arise as a result of e-mail transmission. Future Technology > > Devices International Ltd has taken every reasonable precaution to ensure > > that any attachment to this e-mail has been swept for viruses. However, we > > cannot accept liability for any damage sustained as a result of software > > viruses and would advise that you carry out your own virus checks before > > opening any attachment. > > > >

2 1

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea@arrl.net>
by Christopher F. Beesley 09 Jan '18

09 Jan '18

Hi David (and others), I'm using default Windows 10 coding/decoding. It works perfectly with almost everything I use, including Word, Access, Excel, Visio, Audition, Winamp, Firefox, EditPad, Paint, an AMR converter, Bulk Rename, and several Canon utilities to name but a few. It also works perfectly with older versions of several of the above. Emails in both directions via Yahoo! and MSN are no problem. I find incorrect punctuation in a fair number of 'Comments' made about various news items as well as the chirp-users messages. It has been suggested that the incorrect punctuation is because of data mis-handling by systems in other countries where the apostrophe is not recognised in their language and the question-mark is substituted at that point. I like that explanation, it fits in with the world-wide nature of Amateur Radio as well as news-item comments from all over the world. Such activities would be out of the control of both the sender and recipient. This has legal implications - the email that someone sends may not look like the email that is received, and therefore will be useless as evidence. Thanks for yours and everyone else's interest, 73, Chris ________________________________ From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> Sent: 08 January 2018 20:00 To: chirp_users(a)intrepid.danplanet.com Subject: chirp_users Digest, Vol 109, Issue 8 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Re: chirp_users Digest, Vol 109, Issue 6 and many others (D.J.J. Ring, Jr.) ---------------------------------------------------------------------- Message: 1 Date: Mon, 8 Jan 2018 02:14:17 -0500 From: "D.J.J. Ring, Jr." <n1ea(a)arrl.net> Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and many others To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Message-ID: <CADO5RbiZU9VbjTVB6G-gO3sNn8rMMr2d6j4u1ED05-O-TG_z3w(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Chris, Check your language settings? What encoding are you using? I use UTF-8 on my desktop for the locale. If someone sends me a different encoding it often appears as you say it does. I am using an Android at the monent, so I have no idea of tge encoding, but probably UTF-8. 73 David N1EA On Jan 6, 2018 3:16 PM, "Christopher F. Beesley" <chrisbees2(a)hotmail.com> wrote: > Hi, Chris here. What's all this utter nonsense that is becoming more and > more common whereby the question mark is used instead of the apostrophe? > I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m > fed up of seeing stuff that won?t read easily because of it. It?s rubbish! > Where did you lot learn English grammar' > > Chris. N.B. All punctuation errors above are deliberate, designed to > emphasise the point of this message. > > > ------------------------------ > *From:* chirp_users-bounces(a)intrepid.danplanet.com < > chirp_users-bounces(a)intrepid.danplanet.com> on behalf of > chirp_users-request(a)intrepid.danplanet.com <chirp_users-request@intrepid. > danplanet.com> > *Sent:* 06 January 2018 20:00 > *To:* chirp_users(a)intrepid.danplanet.com > *Subject:* chirp_users Digest, Vol 109, Issue 6 > > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) > 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) > 4. Re: Fwd: FDTI chip compatibility with Mac > (Nigel A. Gunn G8IFF/W8IFF) > 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) > 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) > 8. Linux PPA problem? (Tom Consodine ND5Y) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Jan 2018 17:31:13 -0600 > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> > Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> > Content-Type: text/plain; charset="us-ascii" > > Here is the answer I got from FTDI regarding their cable chipsets! > Let me ask again: how many of you are Mac iOS users, and where did you get > your cloning cables from? > THanks. > Tip N9MVX > > > Begin forwarded message: > > > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > > Subject: RE: FDTI chip compatibility with Mac > > Date: January 5, 2018 at 16:41:00 CST > > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support < > us.support(a)ftdichip.com> > > > > Tipton: > > > > FTDI does not support iOS. > > > > > > Best Regards, > > > > Cameron Forbes > > Customer Support Engineer > > > > Future Technology Devices International Limited > > 7130 SW Fir Loop > > Tigard, OR 97223-8160 > > Tel: 503.726.5415 > > Fax: 503.547.0987 > > > > > > -----Original Message----- > > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com <n9mvx(a)yahoo.com>] > > Sent: Tuesday, January 02, 2018 8:37 AM > > To: US Support > > Subject: FDTI chip compatibility with Mac > > > > My question has to do with the FTDI chipset and Apple computers. I have > a MacBook Pro with iOS High Sierra version 10.13.2 installed. > > Is your chipset compatible with that iOS? > > Thank you. > > > > Tipton Klamberg > > Mascoutah, Il 62258 > > (618) 670-1502 > > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source= > EmailfooterApril17&utm_medium=EmailfooterApril17&utm_ > campaign=EmailfooterApril17&utm_term=EmailfooterApril17& > utm_content=EmailfooterApril17> > > Registered in Scotland No 136640 > > This message contains confidential information and is intended only for > the individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system. E-mail transmission cannot be > guaranteed to be secure or error-free as information could be intercepted, > lost, destroyed, arrive late or incomplete. The sender therefore does not > accept liability for any errors or omissions in the contents of this > message, which arise as a result of e-mail transmission. Future Technology > Devices International Ltd has taken every reasonable precaution to ensure > that any attachment to this e-mail has been swept for viruses. However, we > cannot accept liability for any damage sustained as a result of software > viruses and would advise that you carry out your own virus checks before > opening any attachment. > >

2 1

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and many others
by Christopher F. Beesley 08 Jan '18

08 Jan '18

Hi, Chris here. What's all this utter nonsense that is becoming more and more common whereby the question mark is used instead of the apostrophe? I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m fed up of seeing stuff that won?t read easily because of it. It?s rubbish! Where did you lot learn English grammar' Chris. N.B. All punctuation errors above are deliberate, designed to emphasise the point of this message. ________________________________ From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> Sent: 06 January 2018 20:00 To: chirp_users(a)intrepid.danplanet.com Subject: chirp_users Digest, Vol 109, Issue 6 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) 4. Re: Fwd: FDTI chip compatibility with Mac (Nigel A. Gunn G8IFF/W8IFF) 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) 8. Linux PPA problem? (Tom Consodine ND5Y) ---------------------------------------------------------------------- Message: 1 Date: Fri, 5 Jan 2018 17:31:13 -0600 From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac To: chirp_users(a)intrepid.danplanet.com Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> Content-Type: text/plain; charset="us-ascii" Here is the answer I got from FTDI regarding their cable chipsets! Let me ask again: how many of you are Mac iOS users, and where did you get your cloning cables from? THanks. Tip N9MVX > Begin forwarded message: > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > Subject: RE: FDTI chip compatibility with Mac > Date: January 5, 2018 at 16:41:00 CST > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support <us.support(a)ftdichip.com> > > Tipton: > > FTDI does not support iOS. > > > Best Regards, > > Cameron Forbes > Customer Support Engineer > > Future Technology Devices International Limited > 7130 SW Fir Loop > Tigard, OR 97223-8160 > Tel: 503.726.5415 > Fax: 503.547.0987 > > > -----Original Message----- > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com] > Sent: Tuesday, January 02, 2018 8:37 AM > To: US Support > Subject: FDTI chip compatibility with Mac > > My question has to do with the FTDI chipset and Apple computers. I have a MacBook Pro with iOS High Sierra version 10.13.2 installed. > Is your chipset compatible with that iOS? > Thank you. > > Tipton Klamberg > Mascoutah, Il 62258 > (618) 670-1502 > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source=EmailfooterApril17&utm_medium=E…> > Registered in Scotland No 136640 > This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, lost, destroyed, arrive late or incomplete. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Future Technology Devices International Ltd has taken every reasonable precaution to ensure that any attachment to this e-mail has been swept for viruses. However, we cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment.

7 10

Re: [chirp_users] Linux PPA problem?
by Dave B 06 Jan '18

06 Jan '18

It seems that the entire Ubuntu Launchpad build computer farm is undergoing kernel patching for the recent Spectre and Meltdown Intel (and a few others) CPU problems. Other project groups have said. Sit tight and await the inevitable flood of updates once that lot is done. 73. Dave G0WBX. On 06/01/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Message: 8 > Date: Sat, 6 Jan 2018 12:46:46 -0600 > From: Tom Consodine ND5Y <nd5y(a)yahoo.com> > Subject: [chirp_users] Linux PPA problem? > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <3aec84c7-5b3e-19fe-cedf-8620a0036639(a)yahoo.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > I'm using Ubuntu linux here and a couple days ago I got the new daily > build available e-mail notice but I never got the new version when I did > a system upgrade. > > Today I looked at the Chirp Launchpad PPA page and it shows the latest > chirp-daily is 20180104 but then it says "5 packages waiting to build". > > Is the PPA broken or something?

2 2

[chirp_users] Linux PPA problem?
by Tom Consodine ND5Y 06 Jan '18

06 Jan '18

I'm using Ubuntu linux here and a couple days ago I got the new daily build available e-mail notice but I never got the new version when I did a system upgrade. Today I looked at the Chirp Launchpad PPA page and it shows the latest chirp-daily is 20180104 but then it says "5 packages waiting to build". Is the PPA broken or something? -- Tom ND5Y

2 1

[chirp_users] Wouxun KG-UV8E KG-UV8T KG-UV8D Plus
by D.J.J. Ring, Jr. 06 Jan '18

06 Jan '18

To all who have been following the work on Wouxun KG-UV8E issue #3943. I uploaded a debug log and I wasn't expecting my username and password to be in plain text, so the entire issue had to be deleted. (Thanks Dan) The project is moved: Wouxun KG-UV8E KG-UV8T KG-UV8D Plus <https://chirp.danplanet.com/issues/5481> https://chirp.danplanet.com/issues/5481 73 David N1EA

1 0