[chirp_users] chirp-daily yaesu ft-991 not present

Dan Clemmensen danclemmensen at gmail.com
Mon Mar 18 08:17:13 PDT 2019


Thanks, Nigel.

I just reviewed kenwood_live.py.  Sure enough, the "live mode" model is
quite different from the "clone mode" model that's implemented in almost
all of the other drivers. Given this driver as a worked example, and
Yaesu's extensive documentation of the FT-991 CAT protocol, it would be
possible  to write (but not debug) a driver for that radio without any need
for the protocol and memory image analyses that comprise the bulk of the
nasty driver work for a clone mode driver. An actual radio would obviously
still be needed for debug and testing.

On Sun, Mar 17, 2019 at 3:40 PM Nigel A. Gunn G8IFF/W8IFF <nigel at ngunn.net>
wrote:

> The driver kenwood_live.py uses CAT commands with a number of Kenwood
> transceivers.
>
>
> On 17 March 2019 at 13:18 Dan Clemmensen <danclemmensen at gmail.com> wrote:
>
> I just looked at the FT-991 manual: I have been making a bunch of
> incorrect assumptions. In contrast to the (very few) radios I know about,
> the FT-991 uses a well-documented data transfer protocol called CAT. CHIRP
> in general is oriented toward radios with undocumented "memory image
> transfer" protocols. It is in theory possible to implement a CHIRP driver
> for the FT-991 without first performing the protocol analysis step. If
> there is already a worked example of a CHIRP driver that supports a radio
> using CAT, then support for the FT-991 "should" be easy. I'm not sure where
> to start looking, though.
>
> In my ignorance, I did not realize that the RMS software probably
> implements CAT for the FT-991, so Amerigo likely assumed that CHIRP would
> do the same. The use of CAT appears to put the FT-991 into the category of
> a "live mode" radio instead of being a "clone mode" radio, And I'm only
> familiar with CHIRP "clone mode".
>
> On Fri, Mar 15, 2019 at 12:39 PM Dennis Wage < dwage at dwage.com> wrote:
>
> I think what he meant was:
> my problem is now the chirp for program the Yaesu FT-991 via Cat ( USB-USB
> ), under Windows 10 with RMS Software no problem,
>
> This means he has used the 991 with RMS with the USB to USB cable showing
> us that it works.
>
>  in the actual chirp version i did not can choose the FT-991 from the
> dropdown list.
>
> This means he can't choose it because it's not there.
>
> Dennis M. Wage (W9BOQ)
>
> 245 Corum Hill Road
> Castalian Springs, TN 37031
> (615) 310-4242  Cell
> (615) 562-5128 Home
> http://hammondb3organ.net
> http://overdubs.net
>
>
> On Fri, Mar 15, 2019 at 12:24 PM Dan Clemmensen < danclemmensen at gmail.com>
> wrote:
>
> Amerigo, I don't completely understand your question. CHIRP is not a
> subsisitute for RMS (Winlink) software. Instead, CHIRP replaces or augments
> the Yaesu programming software for for your radio. You can possibly
> (probably) run your RMS Windows software on your Linux Mint system by
> running it under Wine, and you can almost certainly run the Yaesu software
> under Wine.
>
> If you are asking about support for the FT-991 within CHIRP, then sorry,
> it's not there. CHIRP is Open Source software written entirely by unpaid
> volunteers who like to program and who like Ham radio. Each radio type
> needs to be separately analysed and a driver program written for it. The
> volunteer will need physical access to a radio to perform the analysis, and
> will need an absolute minimum of (say) 10 hours of work.  A volunteer who
> can do this in 10 hours can probably make more than $200/hr on a paid
> contract, so clearly this must be a "labor of love". Mere mortals will take
> longer than 10 hours. My guess is that in general a volunteer might program
> a CHIRP driver for a radio that they have chosen to use themselves, but are
> less likely to program for some random new radio unless there is a change
> that the new radio turns out to just need a minor modification or
> adaptation of an existing driver.
>
> Speaking personally, I am a new CHIRP developer (and a new Ham). I
> purchased a Yeasu FT-4 before I had even heard of CHIRP, and was unhappy
> because I later discovered that CHIRP would be highly desirable in my
> application but the radio was unsupported. So, I wrote a CHIRP driver for
> it, and incidentally also for the FT-65, since they are very, very
> similar.  It's been a whole lot of fun, but it took multiple weeks of
> effort. From a purely financial perspective, it would have made far more
> sense to just buy a supported radio or even go out and get a 1-week
> programming gig and then go buy an even more expensive radio.
>
> If you have any programming experience, Please consider trying to write a
> driver. It's really quite fun. Even if you don't have programming
> experience, you might want to try to do an initial analysis if the
> protocol, using some variation of the techniques described at :
>     https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio
>
> On Thu, Mar 14, 2019 at 10:51 PM americo aldighieri <
> americo at aldighieri.ch> wrote:
>
> dear all,
>
> my name is amerigo, my QTH ist Tuggen / Switzerland. Ing. Informatic and
> Electronic
>
> since 2 week all my systems are running under Linux Mint 19.1 , so far ,
> so good.
>
> my problem is now the chirp for program the Yaesu FT-991 via Cat ( USB-USB
> ), under Windows 10 with RMS Software no problem, in the actual chirp
> version i did not can choose the FT-991 from the dropdown list.
>
> is there anybody, who can help me?
>
> Asus Z87-Pro MB with 32GB RAM, Quadcore Intel i47xx, 120GB SSD and more
>
> Linux Mint Version 19.1 with latest patches installed
>
> the command "lsusb" show that the Cygnal Integrated Product CP210x UART
> Bridge succesfully activ with Device 014
>
> best regards from tuggen
> amerigo , hb9gii , 73
> _______________________________________________
> 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
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Dennis Wage at dwage at dwage.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
>
> _______________________________________________
> 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
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Nigel Gunn, W8IFF at nigel at ngunn.net
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
>
>
> Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937
> 825 5032
> Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel at ngunn.net www
> http://www.ngunn.net
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190318/3b64d009/attachment-0002.html 


More information about the chirp_users mailing list