- Users - lists.chirpmyradio.com

[chirp_users] Fwd: FDTI chip compatibility with Mac
by T.E. Klamberg Klamberg 05 Jan '18

05 Jan '18

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.

5 5

[chirp_users] Zastone D9000
by ortingwing＠aol.com 04 Jan '18

04 Jan '18

I have a Zastone D9000. Are there any plans to include Chirp software for this radio, or are there any existing builds that will work for this radio?

1 0

[chirp_users] Find "lost" Chirp fils
by Peter Ryan 04 Jan '18

04 Jan '18

Thanks for all who responded to my query. I learned a great deal...especially that CHIRP is not a "stand alone" app, and stores lists in other areas. With that knowledge, I am now sure I can figure out my inputting mistakes, as to why my additions to the initial list (and in the separate "missing" list) don't seem to get saved, even though I use the SAVE button religiously. With all your great responses, I am confident I will find what I am doing wrong. Thanks very much to all responders, and to the authors of CHIRP. It is really needed.

1 0

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

04 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-20180104 A list of the changes included in this build (since the last daily) follows: Changes for Build #511 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Baofeng BF-T1] FM callback correction, fixes #4933 Last patch introduced a bug in the FM callback, this one fix it.

1 0

[chirp_users] THIRD REQUEST: How to hit up hidden frequecy lists?
by Peter Ryan 03 Jan '18

03 Jan '18

Geez, guys. My question seems like an easy one to answer. Will no one respond to my issue? I saved a new programming list to CHIRP (Macbook/Valley Enterprise cable/Yaesu FT-60) but I can't find it. One other earlier list shows in the "menu bar", but how do I find the second list? I new-named it, and then re-"saved" the list every 10 frequencies. Where the devil does it live, and how do I get it front-and-center when I need to upload it to a new radio? Or if the software reads my "new list" as no more than added frequencies to the initial one, why are the new frequencies not showing in the original list? Thanks

6 5

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

03 Jan '18

Hi. Other than for software that just isn't available for anything other than Windows, there is no reason whatsoever to try to use WINE to run Chirp under Linux. Just go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download And follow the instructions how to get the version you need for your OS. There is even a "Live CD" (bootable self contained system) version! As well as the ability to run it directly from a "tarball" file once the contents are extracted. https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux I do have some Windows specific programs that I need to use, that do run well under WINE, but sadly the DMR codeplug software from Motorola will not install, as the installer needs .NET version whatever, and the Mono equivalent tools are not compatible. All my other radio programming and configuring needs are happily done via Chirp running natively under Linux. As to the serial port issue, it's a "symbolic link" that you create, that in effect redirects references to (for example) COM1: to /dev/ttyUSB0 Job done. As you say, instructions are available how to do that from many sources. I would also dispute the assumption re the probably low importance of the handshake lines. Many radio's use them to enter programming mode, enable some esoteric mode, and/or exit from such modes. It is best to use the version of Chirp, that is natively configured for your OS, rather than try to bludgeon it into working via an abstraction layer, that can itself impose "other feature" you may not want.. 73. Dave G0WBX. On 02/01/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > From: Tom Consodine ND5Y <nd5y(a)yahoo.com> > Subject: [chirp_users] USB serial ports and Linux/WINE > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <7d46aaec-b155-f3f6-6697-f339bb204881(a)yahoo.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > I have no problems using USB serial ports with Windows software running > on Linux/WINE. One of the reasons I switched to Linux was one USB cable > I have would work on Windows 7 but not on Windows 10. > > You have to configure the serial port permissions in Linux. There are > instructions for doing that on the Chirp web site. > > If you are using WINE 2.8 or later you might have to configure the port > settings in WINE or manually make a "registry" key. There are > instructions for doing that on their web site at > > https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#Seri… > > Versions before that only require making a link in the wine folder to > the port. > > Older versions of WINE before about 1.7 don't support all the RS-232 > lines. This probably isn't an issue for radio programming cables that > only use TXD and RXD lines but it is if you need the RTS, CTS, DTR, DSR > lines to work properly.

3 3

[chirp_users] How to find "missing" program list?
by Peter Ryan 02 Jan '18

02 Jan '18

I saved a new programming list to CHIRP (Macbook/Valley Enterprise cable/Yaesu FT-60) but I can't find it. One other earlier list shows in the "menu bar", but how do I find the second list? I new-named it, and then re-"saved" the list every 10 frequencies. Where the devil does it live, and how do I get it front-and-center when I need to upload it to a new radio? Thanks

1 0

Re: [chirp_users] CHIRP and Mac High Sierra
by Dave B 01 Jan '18

01 Jan '18

Hi again. Other thought. Are you running as a user with "permissions" to use Serial ports? In some of the Linux world, that'd be, as a member of the "Dialout" group. (I have no idea if Mac OS, though based on BSD uses the same scheme.) Do you have other USB/serial port adapter using equipment/gadgets that do work OK, if so you could look into and find out how that references attached USB<>RS232 devices. Also, after some googling (Always your first port of call) I see others with similar problems, who found that using an external USB hub device (connected via the Thunderbolt main port) allowed all sorts of "other" vendor kit to work, that just would not when connected directly to the Mac. (Mac Mini's in those cases I think.) Maybe the Serial adapters are asking for too much power? Unlikely, but? Lastly, you say you "Ran all the terminal codes." but you don't actually list exactly what you tried, and what the results were. I don't know how exactly, but I suspect that even Mac's have a command line option, or even a GUI tool, to examine what hardware you have connected to what port and tell you how it would appear to an application, or tell you why it can't be used. I see many Mac users attempting to use them for Ham Radio work. Unless they are using pre-made commercial applications designed and built for Mac's, they usually have lots of trouble. (There are exceptions.) You need to list the exact computer model, specification and version you have, the exact OS version you're running, plus any error or alert messages you get, from commands you try. Then, someone else here who's also a Mac user will probably be able to guide you through the maze and hopefully get it sorted. 73. Dave G0WBX. On 01/01/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > From: Parrish Roberson <psound18(a)yahoo.com> > Subject: Re: [chirp_users] chirp_users Digest, Vol 108, Issue 19 > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: <EEEF6D1B-57BA-4C77-8F65-7333B85FBC63(a)yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Ran all the terminal codes. Doesn?t see the port or cable on the Mac or on parallels tried 2 different BaoFeng cables. Odd they would both be bad. Hopefully it will work soon. Thanks

2 1

[chirp_users] CHIRP and Mac High Sierra
by T.E. Klamberg Klamberg 01 Jan '18

01 Jan '18

Thanks for adding me to the mailing list. I have two Yaesu radios, FT-60 dual bander and FT-2900 2m mobile. I would like to use programming software to set up both radios. It seems that my biggest problem is I have a Mac laptop and not a PC. RT Systems carries a great amount of radios that they have the software for, but it is all Windows driven and apparently work arounds for Mac are a lot of trouble. So much for RT Systems. I have heard from members of my ARC that CHIRP is really the only way to go, until I tell them I have a Mac. Many told me, “Good luck! You’re on your own”. It is strange that Mac users, with ham radio, are left out in the cold. I have a MacBook Pro with a 2.5 GHz Intel Core i5 processor. I have macOS High Sierra, Ver 10.13.2. From what I have seen on the CHIRP website, High Sierra has not been interfaced with CHIRP, yet. Before I spend money on programming cables for either of my radios, I need to know if my OS will be compatible with CHIRP and, not being a software geek on Apple products, how much pain may I encounter with loading CHIRP and successfully using a CSV file to program frequencies into either of my Yaesu rigs. I appreciate any insight or help you may be able to provide me. Thank you. Tip Klamberg N9MVX Mascoutah, IL 62258

9 8

Re: [chirp_users] chirp_users Digest, Vol 108, Issue 19
by Dave B 01 Jan '18

01 Jan '18

The only info I'd add, is to find out how to prevent your OS from sleeping an application and also from powering down what it things are unused USB ports. I'm not a Mac owner/user, but I hear that "AppNap" causes *A LOT* of issues. Also, research and find out how the serial ports are identified on your particular system, and how to search for those that *Really* exist. Mac OS's are based on BSD, so there might be some help there. Find out how to get to a command line terminal display, and learn the basics of how to search for and do stuff there. Just as the rest of us with other 'Nix related boxes have learnt. (ls /dev/ttyUSB* for example will list the real existing ports on a debian/ubuntu based Linux system.) dave@G0WBX-Dell-System-XPS-L502X ~ $ ls /dev/ttyUSB* /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3 That is on my Linux Mint box, but Mac's / BSD's etc will almost certainly have something similar. "|ls /dev/tty.*"| As one website I found indicates... Not having a mac here, I cant test that. Also, as Randy said, steer clear of clone chip-sets. ONLY buy stuff like that from authorised resellers, not eBay. Disclaimer! I have had good genuine stuff from eBay, but I've also had a lot of clone rubbish. (I did have one chip that was physically marked up with the FTDI logo and part number etc, but when connected to a computer, it announced itself as a Prolific chip! I felt sorry for the seller, who was non technical, just acting as a re-seller themselves. We figured out he had over a thousand fake devices. He was not happy, but apologised gave me a full refund without asking, and took the devices back. For that alone I gave him good feedback.) Yes, it'll probably cost more from DigiKey or ??? But you'll know you have the "Genuine" article, and if it proves otherwise, you can return it. "Silicon Labs" (SiLabs) devices are good too. Linux recognises them OK, I have no idea regarding Mac OS's. It has to be said though, that a lot of the current clones are actually quite functional, unless you want to do something special, like re-assign the I/O pins, as you are supposed to be able to do with FTDI parts. (A useful feature, for radio programming leads.) Lastly, don't trust pre-made leads from eBay. Again, I'm sure there are good ones, but again I've also found via others experiences, that there is a lot of stuff there is wired wrong, & very wrong at times! (Mind you, some of the radio manuals are very misleading in this respect too.) Best if possible to build your own programming cables. It's not difficult at all, it just takes a little time to learn about it, and build and test etc. But, in the long term, you can then build/adapt a cable "on the fly" when needed. 73 and Happy New Year to All of the Chirp team. Dave G0WBX. On 31/12/17 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Message: 3 > Date: Sun, 31 Dec 2017 12:35:30 -0500 > From: Randy Elliott <ve3jpu(a)me.com> > Subject: Re: [chirp_users] CHIRP and Mac High Sierra > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: <4543A440-314F-44B8-9641-92226A46E796(a)me.com> > Content-Type: text/plain; charset="windows-1252" > > Hi Tip > > First off, don't let your PC buddy's steer you off track. Using a Mac is not an issue. I have 2 iMacs and 1 Mac book, one of the iMacs and the Mac Book is 11 years old and still going strong. I use Chirp on them all the time. > Make sure the USB to serial adapter has a legitimate chip set in it and not some Chinese rip off. Personally I use adapters with the FTDI chip set in them, but Prolific chip set are equally as good. > The only issue I can see you "might" have is the fact that you up-graded to High Sierra, but I'm not sure about that. I have held off up-grading my newer iMac so far. > Check the web site of the 2 chip set manufacturers I mentioned above, to see if their drivers are compatible with High Sierra. > Hope this helps > > 73 Randy VE3JPU

3 3