<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
.x_MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">I just got a Baofeng UV-5R from Amazon. It shows Firmware Version BFB298</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I’m using the FTDI cable for my Wouxun KG-UV3D to program it.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">The Baofeng OEM software Reads and writes fine to the radio with this cable.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Chrip 03/14/19 gives the following error “Radio refused to send second block 0x1f00”</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Any ideas as to what may be going on here</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Todd</p>
<p class="x_MsoNormal">AD7VB</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">
Mail</a> for Windows 10</p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="border:none; padding:0in"><b>From: </b><a href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.danplanet.com</a><br>
<b>Sent: </b>Saturday, March 16, 2019 12:04 PM<br>
<b>To: </b><a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<b>Subject: </b>chirp_users Digest, Vol 123, Issue 16</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send chirp_users mailing list submissions to<br>
chirp_users@intrepid.danplanet.com<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
or, via email, send a message with subject or body 'help' to<br>
chirp_users-request@intrepid.danplanet.com<br>
<br>
You can reach the person managing the list at<br>
chirp_users-owner@intrepid.danplanet.com<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of chirp_users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: chirp-daily yaesu ft-991 not present (Dennis Wage)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 15 Mar 2019 14:38:50 -0500<br>
From: Dennis Wage <dwage@dwage.com><br>
Subject: Re: [chirp_users] chirp-daily yaesu ft-991 not present<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CAE1d060TRiQRzAE9_dHtT01gyBboEfiPdkdXLZ2ROpH-N6K-aQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I think what he meant was:<br>
my problem is now the chirp for program the Yaesu FT-991 via Cat ( USB-USB<br>
), under Windows 10 with RMS Software no problem,<br>
<br>
This means he has used the 991 with RMS with the USB to USB cable showing<br>
us that it works.<br>
<br>
in the actual chirp version i did not can choose the FT-991 from the<br>
dropdown list.<br>
<br>
This means he can't choose it because it's not there.<br>
<br>
Dennis M. Wage (W9BOQ)<br>
<br>
245 Corum Hill Road<br>
Castalian Springs, TN 37031<br>
(615) 310-4242 Cell<br>
(615) 562-5128 Home<br>
<a href="http://hammondb3organ.net">http://hammondb3organ.net</a><br>
<a href="http://overdubs.net">http://overdubs.net</a><br>
<br>
<br>
On Fri, Mar 15, 2019 at 12:24 PM Dan Clemmensen <danclemmensen@gmail.com><br>
wrote:<br>
<br>
> Amerigo, I don't completely understand your question. CHIRP is not a<br>
> subsisitute for RMS (Winlink) software. Instead, CHIRP replaces or augments<br>
> the Yaesu programming software for for your radio. You can possibly<br>
> (probably) run your RMS Windows software on your Linux Mint system by<br>
> running it under Wine, and you can almost certainly run the Yaesu software<br>
> under Wine.<br>
><br>
> If you are asking about support for the FT-991 within CHIRP, then sorry,<br>
> it's not there. CHIRP is Open Source software written entirely by unpaid<br>
> volunteers who like to program and who like Ham radio. Each radio type<br>
> needs to be separately analysed and a driver program written for it. The<br>
> volunteer will need physical access to a radio to perform the analysis, and<br>
> will need an absolute minimum of (say) 10 hours of work. A volunteer who<br>
> can do this in 10 hours can probably make more than $200/hr on a paid<br>
> contract, so clearly this must be a "labor of love". Mere mortals will take<br>
> longer than 10 hours. My guess is that in general a volunteer might program<br>
> a CHIRP driver for a radio that they have chosen to use themselves, but are<br>
> less likely to program for some random new radio unless there is a change<br>
> that the new radio turns out to just need a minor modification or<br>
> adaptation of an existing driver.<br>
><br>
> Speaking personally, I am a new CHIRP developer (and a new Ham). I<br>
> purchased a Yeasu FT-4 before I had even heard of CHIRP, and was unhappy<br>
> because I later discovered that CHIRP would be highly desirable in my<br>
> application but the radio was unsupported. So, I wrote a CHIRP driver for<br>
> it, and incidentally also for the FT-65, since they are very, very<br>
> similar. It's been a whole lot of fun, but it took multiple weeks of<br>
> effort. From a purely financial perspective, it would have made far more<br>
> sense to just buy a supported radio or even go out and get a 1-week<br>
> programming gig and then go buy an even more expensive radio.<br>
><br>
> If you have any programming experience, Please consider trying to write a<br>
> driver. It's really quite fun. Even if you don't have programming<br>
> experience, you might want to try to do an initial analysis if the<br>
> protocol, using some variation of the techniques described at :<br>
> <a href="https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio">
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio</a><br>
><br>
> On Thu, Mar 14, 2019 at 10:51 PM americo aldighieri <americo@aldighieri.ch><br>
> wrote:<br>
><br>
>> dear all,<br>
>><br>
>> my name is amerigo, my QTH ist Tuggen / Switzerland. Ing. Informatic and<br>
>> Electronic<br>
>><br>
>> since 2 week all my systems are running under Linux Mint 19.1 , so far ,<br>
>> so good.<br>
>><br>
>> my problem is now the chirp for program the Yaesu FT-991 via Cat (<br>
>> USB-USB ), under Windows 10 with RMS Software no problem, in the actual<br>
>> chirp version i did not can choose the FT-991 from the dropdown list.<br>
>><br>
>> is there anybody, who can help me?<br>
>><br>
>> Asus Z87-Pro MB with 32GB RAM, Quadcore Intel i47xx, 120GB SSD and more<br>
>><br>
>> Linux Mint Version 19.1 with latest patches installed<br>
>><br>
>> the command "lsusb" show that the Cygnal Integrated Product CP210x UART<br>
>> Bridge succesfully activ with Device 014<br>
>><br>
>> best regards from tuggen<br>
>> amerigo , hb9gii , 73<br>
>> _______________________________________________<br>
>> chirp_users mailing list<br>
>> chirp_users@intrepid.danplanet.com<br>
>> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
>> This message was sent to Dan Clemmensen at danclemmensen@gmail.com<br>
>> To unsubscribe, send an email to<br>
>> chirp_users-unsubscribe@intrepid.danplanet.com<br>
><br>
> _______________________________________________<br>
> chirp_users mailing list<br>
> chirp_users@intrepid.danplanet.com<br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
> This message was sent to Dennis Wage at dwage@dwage.com<br>
> To unsubscribe, send an email to<br>
> chirp_users-unsubscribe@intrepid.danplanet.com<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190315/d14eeb21/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190315/d14eeb21/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
<br>
End of chirp_users Digest, Vol 123, Issue 16<br>
********************************************<br>
</div>
</span></font>
</body>
</html>