[chirp_users] Programming Yaesu Radios using CHIRP

John Wuest jhwuest at gmail.com
Thu Mar 28 08:26:39 PDT 2019


The FT2600 is not listed as being supported at this time.
https://chirp.danplanet.com/projects/chirp/wiki/Home

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Mar 28, 2019 at 9:07 AM Angelo T Sonnesso <asonnesso at gmail.com>
wrote:

> Will Chirp support the Yaesu FT2600M?
>
>
>
> 73 N2DYN Angelo
>
>
>
> *From:* chirp_users-bounces at intrepid.danplanet.com <
> chirp_users-bounces at intrepid.danplanet.com> *On Behalf Of *Dan Clemmensen
> *Sent:* Thursday, March 28, 2019 12:17 AM
> *To:* Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> *Subject:* Re: [chirp_users] Programming Yaesu Radios using CHIRP
>
>
>
> There are a lot of Yaesu radios, and not all of them use the same
> programming protocol. I'm only really familiar with the newer Yaesu HTs,
> namely the FT-4 and FT-65. The protocol for these radios controls the
> memory access fairly tightly, so accidentally writing into the wrong place
> is unlikely. You can access memory you are not supposed to by writing
> special software, but the CHIRP driver does not do this.  Older Yaesu
> radios use a much cruder protocol and it is theoretically possible to mess
> up and hit the wrong memory, but I don't personally have knowledge of this,
> we will need to see who else responds.
>
>
>
> On Wed, Mar 27, 2019 at 9:06 PM Larry Lovell <larry.lovell76 at gmail.com>
> wrote:
>
> 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.
>
>
>
> --
>
> 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
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
> <#m_-7284464311336039553_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to John Wuest at jhwuest 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/20190328/2fa86d9b/attachment-0002.html 


More information about the chirp_users mailing list