- Users - lists.chirpmyradio.com

Re: [chirp_users] Programming Yaesu Radios using CHIRP search tip
by Gary Craig 08 Apr '19

08 Apr '19

Aubrey thanks for the tip on searching! I was going to download all of the archives into a folder to search from but they are g-zipped and I'm running windows. Haven't found a compatible program i can use. Be blessed! May 2019 be our year of change & growth! Gary Craig KI5CCD Maintenance Webco Industries Texas Distribution 750 Martin Luther King Jr Dr Orange, TX 77630-3094 409-886-0807 ext. 107 Fax 918-246-7045 gcraig(a)webcotube.com<mailto:gcraig@webcotube.com> From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> On Behalf Of Aubrey Turner Sent: Thursday, April 4, 2019 9:28 AM To: chirp_users(a)intrepid.danplanet.com Subject: Re: [chirp_users] Programming Yaesu Radios using CHIRP This email originated from an external sender. Use caution when following links or opening attachments as they could be malicious There doesn't appear to be an "official" way to search the archives, but you can use Google's "site" directive to do it. For example, if I want to search for "Raspberry" (i.e. Raspberry Pi), then I can put the following into the Google search bar: "site:intrepid.danplanet.com/pipermail/chirp_users/ raspberry" On 4/4/19 9:23 AM, sam walton wrote: I'm personally fascinated by your results. As far as I know there is no way to search this mailing list to filter for topics like this? Happy to be pointed to instructions. Are there resources for learning how to integrate boards like the RPi with radios like my Baofeng? Or is this knowledge mostly around the Direwolf community? thx, sam452 On Apr 3, 2019, at 11:16 PM, Dan Clemmensen <danclemmensen(a)gmail.com<mailto:danclemmensen@gmail.com>> wrote: I ran CHIRP successfully on a Raspberry Pi Zero W (Pi0W) as an experiment to see if I could eliminate the need for a USB-to-Serial cable. It worked. Many modern HTs use a 3.3V serial interface, which is what the Pi0W exposes on its header pins. I just connected the Pi0W's RxD, TxD, and GND to the appropriate pins on the Baofeng UV-5RA. with 2K resistors in the RxD and TxD wires and just a straight wire for GND. It worked. CHIRP did take a very long time to get itself initrialized the first time. I think that is because the Pi0W is a slow single-CPU machine. For packet, I intended to use the Pi0W, running Direwolf, but I'm now shifting to the FriendlyArm NanoPi Duo, because is has on-board audio I/O which eliminates the need for a USB audio dongle. The NanoPi is also only about half the size of the Pi0W and it has four CPUs. The downside is that it is not as well supported, so I'm on my own for pretty much everything. I have CHIRP running on the NanoPi Duo now. I intend to see if I can build a CHIRP wire for my Yaesu FT-4. On Wed, Apr 3, 2019 at 8:47 PM Larry Lovell <larry.lovell76(a)gmail.com<mailto:larry.lovell76@gmail.com>> wrote: Thanks, I mentioned the other platforms. Right now, I am trying to get Packet and then APRS running on my Raspberry Pi. I will try CHIRP on it as well. On Wed, Apr 3, 2019 at 8:04 PM Chuck Hast <kp4djt(a)gmail.com<mailto:kp4djt@gmail.com>> wrote: Also do not forget it runs on the major platforms, i.e. It started out on Linux and is of course available for Windows (as you have presented) and Mac. I believe it will also run under BSD. A lot of us like to run it on a Raspberry Pi. On Tue, Apr 2, 2019 at 6:57 PM Amnon Zohar <amnon.zohar(a)gmail.com<mailto:amnon.zohar@gmail.com>> wrote: remark for your presentation the cheap cables with clone prolific chips works fine with the older driver version 3.2.0.0 a good source for technical staff can be found at www.miklor.com<http://www.miklor.com/> (the bible ofradios) you can download that driver there.... ‫בתאריך יום ג׳, 2 באפר׳ 2019 ב-23:44 מאת ‪Larry Lovell‏ <‪larry.lovell76(a)gmail.com<mailto:larry.lovell76@gmail.com>‏>: I wish to thank all of you for your findings on the Yaesu radios. I am giving a presentation on CHIRP to our local (Eastern Idaho) HAMs tonight. If you are interested, the PDF of my presentation is located at: http://www.qrvtronics.com/CatHAM_Radio/files/UsingCHIRPorOtherSoftware.pdf On Thu, Mar 28, 2019 at 10:36 PM <chirp.cordless(a)xoxy.net<mailto:chirp.cordless@xoxy.net>> wrote: Well there's some truth there, but what truth I'm aware of should not scare anyone off from using chirp with Yaesus. Back in early 2014 I was doing some chirp code development on FT-60s, fixing some bugs and with the eventual goal of adding "Settings" control. Someone else has since done that. Part of that process is mapping the memory by twiddling bits in the image, uploading to the radio, and seeing through the radio's button interface what changed. It went pretty smoothly for a while, then I managed to brick *TWO* FT-60s. One of which was repaired by sending it to the factory to replace an eprom. I'm not going to add any further detail here, my investigation was pretty thoroughly documented in a thread on the chirp_devel mail list with subject "How to brick an FT-60" starting 3/22/14. See also Bug #1547: [FT-60] Chirp should check parity on download. But normal use of chirp to program radios doesn't do this. The user interface only lets you make limited, well understood changes to the radio image bitmap. I still do that with mine. -dan > Date: Wed, 27 Mar 2019 22:05:06 -0600 > From: Larry Lovell <larry.lovell76(a)gmail.com<mailto:larry.lovell76@gmail.com>> > Subject: [chirp_users] Programming Yaesu Radios using CHIRP > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com>> > > Has anyone had a problem programming a Yaesu radio with CHIRP? > Someone mentioned that their Yaesu was damaged and had to be sent to the > factory because CHIRP had overwritten some code controlling the processor. > It also had to be re-flashed. > Since I don't fully understand how CHIRP works this doesn't make sense to > me, but knowing manufacturing companies, they may share Channel Memory with > processor memory and not think much about it. > Thanks for your information. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Larry Lovell at larry.lovell76(a)gmail.com<mailto:larry.lovell76@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> -- Larry Lovell 73's N7RGW http://QRVTronics.com<http://qrvtronics.com/> Cell: 214-697-1729 _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar(a)gmail.com<mailto:amnon.zohar@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> -- Amnon _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt(a)gmail.com<mailto:kp4djt@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> -- Chirp + Editcp + MD380Tools on Linux Celestial!!! Chuck -- KP4DJT _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Larry Lovell at larry.lovell76(a)gmail.com<mailto:larry.lovell76@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> -- Larry Lovell 73's N7RGW http://QRVTronics.com<http://qrvtronics.com/> Cell: 214-697-1729 _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen(a)gmail.com<mailto:danclemmensen@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Sam at sam(a)foofrancine.com<mailto:sam@foofrancine.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com<mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Aubrey Turner at aubrey.c.turner(a)gmail.com<mailto:aubrey.c.turner@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com<mailto:chirp_users-unsubscribe@intrepid.danplanet.com>

3 2

[chirp_users] Chirp help
by ______ ______ 08 Apr '19

08 Apr '19

Hi im not sure if this is the proper place for this but I'm having issues programming my radio to work with the rest of the radios at work. I'm new to all of this stuff and I'm not sure where all of the things from the form they send me go

5 6

Re: [chirp_users] Help! Mac v10.14.5
by Justin R 06 Apr '19

06 Apr '19

Good Evening Everyone; I am running into an issue trying to get my Baofang UV-5R to clone to CHIRP. I am currently running the newest version on mac v10.14.5 and have downloaded and attempted to use all the drivers mentioned on the CHIRP website and any other blogs I could find discussing the issue. The cable I am using is "BTECH PC03 FTDI Genuine USB Programming Cable for BTECH, BaoFeng, Kenwood, and AnyTone Radio" off amazon. If you go to the Baofang website it redirects you to this cable on amazon. Overall I am just stuck, any help would be greatly appreciated.Thank you for your time and consideration. Cheers! Justin On Sat, Apr 6, 2019 at 8:53 PM Justin R <armatiage2001(a)gmail.com> wrote: > Good Evening Everyone; > I am running into an issue trying to get my Baofang UV-5R to clone to > CHIRP. I am currently running the newest version on mac v10.14.5 and have > downloaded and attempted to use all the drivers mentioned on the CHIRP > website and any other blogs I could find discussing the issue. The cable I > am using is "BTECH PC03 FTDI Genuine USB Programming Cable for BTECH, > BaoFeng, Kenwood, and AnyTone Radio" off amazon. If you go to the Baofang > website it redirects you to this cable on amazon. Overall I am just stuck, > any help would be greatly appreciated.Thank you for your time and > consideration. > > Cheers! > Justin >

3 5

[chirp_users] REPORT: Direct connect from Pi to Yaesu FT-4 succeeds
by Dan Clemmensen 05 Apr '19

05 Apr '19

The FT-4 also uses a 3.3v serial connection for programming, but it's 2-wire, meaning the Tx and Rx are both on the same wire, named DATA. I use the NanoPi Duo's serial port pins (Tx and Rx) and GND. The FT-4 presents GND on the 2.5mm MIC sleeve, and DATA on the 2.5mm MIC ring. I connected GND directly to Pi GND,Data directly to Pi RxD, and Pi via a 2K resistor to DATA. CHIRP successfully downloaded and uploaded. So, we have two worked examples of modern HTs directly connecting to the 3.3V serial ports of modern tiny SBCs.

1 0

[chirp_users] Report: Direct connect from RPi to BaoFang succeeds
by Dan Clemmensen 05 Apr '19

05 Apr '19

I have now successfully downloaded and uploaded a Baofang UV-5RA using a Raspberry Pi and using a NanoPi Duo, with not USB dongle. The programming cable consists of three wires and the connectors at each end, and nothing else. function radio Pi GND 2.5mm SP sleeve GND Data FROM radio 2.5mm SP ring RxD Data TO radio 3.5mm MIC sleeve TxD Run CHIRP on your RPi, and it just works.

1 0

[chirp_users] FT70 fails to download
by Dennis Carr 04 Apr '19

04 Apr '19

Howdy! Running a Yaesu Ft-70DR that just arrived today. First thing's first: download to Chirp! Running daily 20190221 on Debian current stable, using the builds from the website. Just one problem - it didn't download. After following instructions (battery off, DC and USB in (specifically the USB cable that came with), hold AMS key while powering on, select Download option, set the right options (/dev/ttyACM0, Yaesu FT-70D)), hit the BAND button so it says TX, and... ...no activity. It times out, radio shows ERROR. Long and short, I'm not sure if I'm doing something wrong here. So in short: * What am I missing? * What other information is needed from me to properly answer? -Dennis KE7KIF

3 13

Re: [chirp_users] Programming Yaesu Radios using CHIRP
by chirp.cordless＠xoxy.net 04 Apr '19

04 Apr '19

Well there's some truth there, but what truth I'm aware of should not scare anyone off from using chirp with Yaesus. Back in early 2014 I was doing some chirp code development on FT-60s, fixing some bugs and with the eventual goal of adding "Settings" control. Someone else has since done that. Part of that process is mapping the memory by twiddling bits in the image, uploading to the radio, and seeing through the radio's button interface what changed. It went pretty smoothly for a while, then I managed to brick *TWO* FT-60s. One of which was repaired by sending it to the factory to replace an eprom. I'm not going to add any further detail here, my investigation was pretty thoroughly documented in a thread on the chirp_devel mail list with subject "How to brick an FT-60" starting 3/22/14. See also Bug #1547: [FT-60] Chirp should check parity on download. But normal use of chirp to program radios doesn't do this. The user interface only lets you make limited, well understood changes to the radio image bitmap. I still do that with mine. -dan > Date: Wed, 27 Mar 2019 22:05:06 -0600 > From: Larry Lovell <larry.lovell76(a)gmail.com> > Subject: [chirp_users] Programming Yaesu Radios using CHIRP > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > > Has anyone had a problem programming a Yaesu radio with CHIRP? > Someone mentioned that their Yaesu was damaged and had to be sent to the > factory because CHIRP had overwritten some code controlling the processor. > It also had to be re-flashed. > Since I don't fully understand how CHIRP works this doesn't make sense to > me, but knowing manufacturing companies, they may share Channel Memory with > processor memory and not think much about it. > Thanks for your information.

10 11

[chirp_users] MDF-A and B
by James Corbin 02 Apr '19

02 Apr '19

How do I switch my Baofeng PC03 from frequency to name? When I go to 21 and 22 for the name, it still only shows frequencies. -- James Corbin

8 14

[chirp_users] Having Receive only on some channels on Baofeng UV-5R + Plus
by Michael Alecksynas 24 Mar '19

24 Mar '19

Hi All, Thanks for Reading. I just programmed up a UV-5R+ Plus for a friend of mine and that worked out good with the Chirp program but there are some Frequencies that I would like to have Receive only on the radio. I went through the program and I didn't see anything listed to do so. Did I overlook it or does this program not have that feature??? Thank you very much in advance for your response back. Mike N2JVENiverville, New York

4 5

Re: [chirp_users] Radio did not respond Baofeng UV-82
by sam walton 22 Mar '19

22 Mar '19

Thank for your help. ls -l /dev/ttyUSB0 (as my regular user) crw-rw—— 1 root dialout 188, 0 Mar 22 00:21 /dev/ttyUSB0 groups sam adm dialout cdrom sudo dip plugdev lpadmin sambashare thx, sam kk4jzh > On Mar 22, 2019, at 2:00 PM, chirp_users-request(a)intrepid.danplanet.com wrote: > > Sam, > > Please do this: > > ls -l /dev/ttyUSB0 > > Send back the output. > > Also send back the output of this when you are using your user (regular) > account: > > groups > > It is important that you are in the group that owns /dev/ttyUSB0 > > I'm not using Ubuntu but Arch Linux, but here is my output to show you: > > ls -l /dev/ttyUSB0 > crw-rw---- 1 root *uucp* 188, 0 Mar 21 09:40 /dev/ttyUSB0 > > [djringjr@n1ea ~]$ groups > video *uucp* wheel djringjr > > I've made *uucp *bold so you can see the important part. > > I believe /dev/ttyUSB0 in Ubuntu is owned by root tty - don't change it! > Just make sure you are a member of whatever group that owns /dev/ttyUSB0. > > Different distros handle devices slightly differently. The point is that > if you are executing CHIRP and you are not a member of the group that owns > the /dev/ttyUSB0 device, it will not work. > > To add a user to a group - whatever group owns the ttyUSB0 - > > sudo adduser user group > > Where user is your user name and group is the group that owns ttyUSB0 > > > 73 > DR > N1EA

3 2