[chirp_users] Programming Yaesu Radios using CHIRP

Wed Apr 3 21:16:00 PDT 2019

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 at 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 at 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 at 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 (the
>>> bible ofradios)
>>> you can download that driver there....
>>>
>>> ‫בתאריך יום ג׳, 2 באפר׳ 2019 ב-23:44 מאת ‪Larry Lovell‬‏ <‪
>>> larry.lovell76 at 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 at 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 at gmail.com>
>>>>> > Subject: [chirp_users] Programming Yaesu Radios using CHIRP
>>>>> > To: Discussion of CHIRP <chirp_users at 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 at intrepid.danplanet.com
>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>> This message was sent to Larry Lovell at larry.lovell76 at gmail.com
>>>>> To unsubscribe, send an email to
>>>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>>>>
>>>>
>>>>
>>>> --
>>>> Larry Lovell
>>>> 73's N7RGW
>>>> http://QRVTronics.com <http://qrvtronics.com>
>>>> Cell: 214-697-1729
>>>> _______________________________________________
>>>> chirp_users mailing list
>>>> chirp_users at intrepid.danplanet.com
>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>> This message was sent to amnon at amnon.zohar at gmail.com
>>>> To unsubscribe, send an email to
>>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>>
>>>
>>>
>>> --
>>> Amnon
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> This message was sent to Chuck Hast at kp4djt at gmail.com
>>> To unsubscribe, send an email to
>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>
>>
>>
>> --
>> Chirp + Editcp + MD380Tools on Linux
>> Celestial!!!
>> Chuck -- KP4DJT
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Larry Lovell at larry.lovell76 at gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>
>
>
> --
> Larry Lovell
> 73's N7RGW
> http://QRVTronics.com <http://qrvtronics.com>
> Cell: 214-697-1729
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Dan Clemmensen at danclemmensen at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190403/b5c9c001/attachment.html 