<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Any news in getting support for radioddity gs5b?<span id="ms-outlook-android-cursor"></span></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of chirp_users-request@intrepid.danplanet.com
<chirp_users-request@intrepid.danplanet.com><br>
<b>Sent:</b> Wednesday, June 24, 2020 12:00:02 PM<br>
<b>To:</b> chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com><br>
<b>Subject:</b> chirp_users Digest, Vol 138, Issue 20</font>
<div> </div>
</div>
<div class="BodyFragment"><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: Baofeng GT-1 can read radio but cannot write (wtforme)<br>
2. Chirp program (George Piek)<br>
3. Re: Chirp program (Jim Unroe)<br>
4. Re: Chirp program (George Piek)<br>
5. Re: Chirp program (Jim Unroe)<br>
6. Re: Radioddity QB25 (Byron Boggs)<br>
7. Re: Chirp program (George Piek)<br>
8. Re: Chirp program (George Piek)<br>
9. Re: Chirp program (Jim Unroe)<br>
10. Re: Radioddity QB25 (Jim Unroe)<br>
11. Re: Radioddity QB25 (Byron Boggs)<br>
12. Re: Radioddity QB25 (Jim Unroe)<br>
13. unable to install (Donald Jacob)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 23 Jun 2020 15:10:22 -0400<br>
From: wtforme <wtforme@hotmail.com><br>
Subject: Re: [chirp_users] Baofeng GT-1 can read radio but cannot<br>
write<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<DM5PR2001MB1722C010C05DC6D42606A8A4BF940@DM5PR2001MB1722.namprd20.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank you. I finally got the factory software to work. I had to turn off<br>
the U ART FIFO BUFFERS.<br>
<br>
On Tue, Jun 23, 2020, 1:54 PM W Paul Mills <ac0hy@wpmills.com> wrote:<br>
<br>
> Make absolutely sure that the cable is fully plugged into the radio. It is<br>
> not unusual for them to not mate up well.<br>
><br>
> On 6/20/20 11:37 PM, wtforme wrote:<br>
><br>
> I have the latest version of chirp installed. I am showing the Prolific<br>
> driver on com 5 and have retrograded it to version 3.2.00. I know it is a<br>
> cheap ass cable but what is baffling me is why I can read but not write.<br>
><br>
> I am running Windows 10.<br>
><br>
> I get the following error: Failed to send block to radio at 0000.<br>
><br>
> Thanks for any hep<br>
><br>
> _______________________________________________<br>
> chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>
> This message was sent to Paul AC0HY at ac0hy@wpmills.com<br>
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
><br>
><br>
> --<br>
> /**************************************************<br>
> * Amateur Radio Station AC0HY *<br>
> * W. Paul Mills SN807 *<br>
> * Assistant EC Alpha-1 ARES Shawnee/Wabaunsee, KS *<br>
> * President Kaw Valley Amateur Radio Club *<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>
> This message was sent to Bob at wtforme@hotmail.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/20200623/e409ddf9/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200623/e409ddf9/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 24 Jun 2020 10:21:39 +0200<br>
From: George Piek <georgepiek7@gmail.com><br>
Subject: [chirp_users] Chirp program<br>
To: chirp_users@intrepid.danplanet.com<br>
Message-ID:<br>
<CALfNQNupsbOz3HyFkAa0h9Tnn0_HVCxgAAKTq9-6H=h9LqJgPQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio.<br>
Suddenly when I request to "Download from Radio" I receive the message "<br>
Not enough data" Why would that be please. I have used it before and had no<br>
problems.<br>
<br>
Regards<br>
George<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/37d27225/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/37d27225/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 24 Jun 2020 08:11:31 -0400<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U6ai82_+PqD-AJGZx7wwBRhhp_hntyiudRVX4-8g9-=Ug@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Wed, Jun 24, 2020 at 4:10 AM George Piek <georgepiek7@gmail.com> wrote:<br>
><br>
> Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio. Suddenly when I request to "Download from Radio" I receive the message " Not enough data" Why would that be please. I have used it before and had no problems.<br>
><br>
> Regards<br>
> George<br>
<br>
Hi George,<br>
<br>
>From the information you have provided, I am going to guess that you<br>
may be selecting the wrong model. Here's why.<br>
<br>
There is no CHIRP driver for any radio model that provides a " Not<br>
enough data" message to the user. The word "enough" doesn't even show<br>
up in any message for any radio driver module. So looking through all<br>
of the Baofeng radio driver modules for messages that contain both<br>
"not" and "data" I find "baofeng_common.py". It contains the following<br>
message: "Error reading data from radio: not the amount of data we<br>
want." Assuming this message is the actual message that you are<br>
seeing, this allows me to get a list of all radio driver modules that<br>
use "baofeng_common.py". They are as follows.<br>
<br>
baofeng_wp970i.py<br>
gmrsuv1.py<br>
mursv1.py<br>
uv6r.py<br>
uv5x3.py<br>
<br>
>From the above list only "baofeng_wp970i.py" and "uv6r.py" use the<br>
Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I<br>
hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the<br>
"Error reading data from radio: not the amount of data we want."<br>
message (screen capture attached).<br>
<br>
Since the "UV-5R" and "UV-6R" selections are visually similar, I think<br>
you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".<br>
<br>
Jim KC9HI<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 2020-06-24 07_49_42-.png<br>
Type: image/png<br>
Size: 6267 bytes<br>
Desc: not available<br>
Url : <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/aa3e2b99/attachment-0001.png">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/aa3e2b99/attachment-0001.png</a>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 24 Jun 2020 15:23:01 +0200<br>
From: George Piek <georgepiek7@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CALfNQNtp_E8335EJP3gLf8_pCrAXfh_Bim4Uy=2Gims5A079hQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi, yes you are correct on the actual msg. No I have made double sure in<br>
selecting the correct radio i.e. UV 5 R. As I said, cannot understand why<br>
because I had downloaded from same radio previously.<br>
<br>
Regards<br>
George<br>
<br>
On Wed, 24 Jun 2020, 14:14 Jim Unroe, <rock.unroe@gmail.com> wrote:<br>
<br>
> On Wed, Jun 24, 2020 at 4:10 AM George Piek <georgepiek7@gmail.com> wrote:<br>
> ><br>
> > Good day to you, I am using Chirp for programming my UV 5 R Baofeng<br>
> Radio. Suddenly when I request to "Download from Radio" I receive the<br>
> message " Not enough data" Why would that be please. I have used it before<br>
> and had no problems.<br>
> ><br>
> > Regards<br>
> > George<br>
><br>
> Hi George,<br>
><br>
> >From the information you have provided, I am going to guess that you<br>
> may be selecting the wrong model. Here's why.<br>
><br>
> There is no CHIRP driver for any radio model that provides a " Not<br>
> enough data" message to the user. The word "enough" doesn't even show<br>
> up in any message for any radio driver module. So looking through all<br>
> of the Baofeng radio driver modules for messages that contain both<br>
> "not" and "data" I find "baofeng_common.py". It contains the following<br>
> message: "Error reading data from radio: not the amount of data we<br>
> want." Assuming this message is the actual message that you are<br>
> seeing, this allows me to get a list of all radio driver modules that<br>
> use "baofeng_common.py". They are as follows.<br>
><br>
> baofeng_wp970i.py<br>
> gmrsuv1.py<br>
> mursv1.py<br>
> uv6r.py<br>
> uv5x3.py<br>
><br>
> >From the above list only "baofeng_wp970i.py" and "uv6r.py" use the<br>
> Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I<br>
> hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the<br>
> "Error reading data from radio: not the amount of data we want."<br>
> message (screen capture attached).<br>
><br>
> Since the "UV-5R" and "UV-6R" selections are visually similar, I think<br>
> you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".<br>
><br>
> Jim KC9HI<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 George Piek at georgepiek7@gmail.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/20200624/bedb802a/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/bedb802a/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 24 Jun 2020 09:51:58 -0400<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U4aGZwJwaGAoGSW6Q1sEOk+3SuPk-q4ojSZBWWwXJtPEw@mail.gmail.com><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com> wrote:<br>
><br>
> Hi, yes you are correct on the actual msg. No I have made double sure in selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.<br>
><br>
> Regards<br>
> George<br>
><br>
<br>
Then please supply some additional information. You've supplied very<br>
little. Such as...<br>
<br>
CHIRP version:<br>
Operating system and version (Windows, Linux, macOS):<br>
Programming cable type (which USB-to-Serial chip is inside):<br>
Attach clean debug.log file:<br>
<br>
The "How To Report Issues" page shows how to find the debug.log file<br>
for all 3 supported operating systems.<br>
<a href="https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues">https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues</a><br>
<br>
A "clean" debug.log file is one where you close CHIRP, open CHIRP,<br>
cause the error and finally close CHIRP.<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 24 Jun 2020 14:01:34 +0000<br>
From: Byron Boggs <kc8ue@hotmail.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<DM6PR07MB6427263109439DE673818BD3EF950@DM6PR07MB6427.namprd07.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I once again contacted Radioddity Support. He installed the factory software, set it up for me and then set up Chirp for me. I have my radio programmed.<br>
He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.<br>
<br>
Sent from Byron Boggs<br>
kc8ue@hotmail.com<br>
<br>
________________________________<br>
From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Jim Unroe <rock.unroe@gmail.com><br>
Sent: Monday, June 22, 2020 10:53:22 AM<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
<br>
On Fri, Jun 19, 2020 at 2:00 PM Jim Unroe <rock.unroe@gmail.com> wrote:<br>
><br>
> On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs <kc8ue@hotmail.com> wrote:<br>
> ><br>
> > I purchased the QB25 with hopes of installing it in my pickup truck. I have two programming cables for it, the one that came with the radio and an FTDI cable that I purchased recently.<br>
> > My problem us error messages. Depending on the port configuration, I get an error message that states it failed to identify the radio, OR the it failed to enter the clone mode. I have tried other variants of this radio like the QTY7900. I have tried
Windows 10 and an old laptop with Windows XP. Same error message on either operating system. Searching through requests I see others have experienced the same issue. I have clicked on the post for that issue but it doesn't do anything and I am at a loss
as to what I need to do. I have used Chirp to program the little UV5R units without issue.<br>
> > Suggestions will be greatly appreciated<br>
> ><br>
> > Byron<br>
> > Kc8ue<br>
><br>
> Hi Byron,<br>
><br>
> Your QB25 most likely has an MCU-Version that is not recognized by<br>
> CHIRP. I recently submitted a patch to add one in May (VC4114) and<br>
> another one in June (VC4104) but the most recent one hasn't been<br>
> accepted yet. There are quite a few patches in the queue to be<br>
> accepted but the process has been slowed down by the Covid-19<br>
> pandemic. Unless it has an even different MCU-Version than the one I<br>
> just added, it will be supported in the next CHIRP daily build. You<br>
> can determine the MCU-Version using the factory programming software.<br>
> It will be shown in the bottom status display area.<br>
><br>
> Jim KC9HI<br>
<br>
Assuming that your radio's MCU-version is VC4114, today's CHIRP daily<br>
build should allow it to be recognized.<br>
<br>
Jim KC9HI<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 Byron at kc8ue@hotmail.com<br>
To unsubscribe, send an email to 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/20200624/697c248f/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/697c248f/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 24 Jun 2020 16:15:59 +0200<br>
From: George Piek <georgepiek7@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CALfNQNuaDCR3BqJT1v1t8AKcyHWBNGN4ODKdxfttd=1-w1ukxg@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
My operating system is Windows 10. Version of Chirp is latest , 20200622<br>
<br>
<br>
On Wed, 24 Jun 2020, 15:54 Jim Unroe, <rock.unroe@gmail.com> wrote:<br>
<br>
> On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com> wrote:<br>
> ><br>
> > Hi, yes you are correct on the actual msg. No I have made double sure in<br>
> selecting the correct radio i.e. UV 5 R. As I said, cannot understand why<br>
> because I had downloaded from same radio previously.<br>
> ><br>
> > Regards<br>
> > George<br>
> ><br>
><br>
> Then please supply some additional information. You've supplied very<br>
> little. Such as...<br>
><br>
> CHIRP version:<br>
> Operating system and version (Windows, Linux, macOS):<br>
> Programming cable type (which USB-to-Serial chip is inside):<br>
> Attach clean debug.log file:<br>
><br>
> The "How To Report Issues" page shows how to find the debug.log file<br>
> for all 3 supported operating systems.<br>
> <a href="https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues">
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues</a><br>
><br>
> A "clean" debug.log file is one where you close CHIRP, open CHIRP,<br>
> cause the error and finally close CHIRP.<br>
><br>
> Jim KC9HI<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 George Piek at georgepiek7@gmail.com<br>
> To unsubscribe, send an email to<br>
> chirp_users-unsubscribe@intrepid.danplanet.com<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/83fec9a8/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/83fec9a8/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Wed, 24 Jun 2020 16:19:38 +0200<br>
From: George Piek <georgepiek7@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CALfNQNsnJxqq=T3ZCYVvqiRiJZA=CCONHFfkBJPa0bDkT-Qh8A@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
And my cable is a Boafeng cable purchased from China shop. As I said, cable<br>
worked before.<br>
<br>
<br>
On Wed, 24 Jun 2020, 16:15 George Piek, <georgepiek7@gmail.com> wrote:<br>
<br>
> My operating system is Windows 10. Version of Chirp is latest , 20200622<br>
><br>
><br>
> On Wed, 24 Jun 2020, 15:54 Jim Unroe, <rock.unroe@gmail.com> wrote:<br>
><br>
>> On Wed, Jun 24, 2020 at 9:26 AM George Piek <georgepiek7@gmail.com><br>
>> wrote:<br>
>> ><br>
>> > Hi, yes you are correct on the actual msg. No I have made double sure<br>
>> in selecting the correct radio i.e. UV 5 R. As I said, cannot understand<br>
>> why because I had downloaded from same radio previously.<br>
>> ><br>
>> > Regards<br>
>> > George<br>
>> ><br>
>><br>
>> Then please supply some additional information. You've supplied very<br>
>> little. Such as...<br>
>><br>
>> CHIRP version:<br>
>> Operating system and version (Windows, Linux, macOS):<br>
>> Programming cable type (which USB-to-Serial chip is inside):<br>
>> Attach clean debug.log file:<br>
>><br>
>> The "How To Report Issues" page shows how to find the debug.log file<br>
>> for all 3 supported operating systems.<br>
>> <a href="https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues">
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues</a><br>
>><br>
>> A "clean" debug.log file is one where you close CHIRP, open CHIRP,<br>
>> cause the error and finally close CHIRP.<br>
>><br>
>> Jim KC9HI<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 George Piek at georgepiek7@gmail.com<br>
>> To unsubscribe, send an email to<br>
>> chirp_users-unsubscribe@intrepid.danplanet.com<br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/0212ab69/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/0212ab69/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Wed, 24 Jun 2020 10:38:57 -0400<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Chirp program<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U5Y78+JV6qJRGEU_v7NsG7yidtGy_P8-7ov9E2X5XN9-A@mail.gmail.com><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, Jun 24, 2020 at 10:28 AM George Piek <georgepiek7@gmail.com> wrote:<br>
><br>
> And my cable is a Boafeng cable purchased from China shop. As I said, cable worked before.<br>
><br>
debug.log?<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Wed, 24 Jun 2020 10:47:24 -0400<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U7o7T3nAPr-gHH+wcggbH3H5-ZAR+2T1w85HpBB7YYiDw@mail.gmail.com><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs <kc8ue@hotmail.com> wrote:<br>
><br>
> I once again contacted Radioddity Support. He installed the factory software, set it up for me and then set up Chirp for me. I have my radio programmed.<br>
> He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.<br>
><br>
> Sent from Byron Boggs<br>
> kc8ue@hotmail.com<br>
<br>
You don't need the factory software. The reason it works now is<br>
because the CHIRP daily build that was issued a couple of days ago<br>
added an additional MCU-Version (which is probably the one your radio<br>
has - VC4114). Prior to that, your radio couldn't be identified. You<br>
can verify this by looking at the following CHIRP setting...<br>
<br>
Settings -> Other Settings -> Fingerprint: {MCU-version}<br>
<br>
The MCU-Version is also displayed in the bottom status display area of<br>
the factory programming software.<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Wed, 24 Jun 2020 15:06:57 +0000<br>
From: Byron Boggs <kc8ue@hotmail.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<DM6PR07MB6427D1062893AAB3F0BE0539EF950@DM6PR07MB6427.namprd07.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Someone asked what the MCU version of my radio was. It is VC4104.<br>
<br>
Sent from Byron Boggs<br>
kc8ue@hotmail.com<br>
________________________________<br>
From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Jim Unroe <rock.unroe@gmail.com><br>
Sent: Wednesday, June 24, 2020 10:47:24 AM<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
<br>
On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs <kc8ue@hotmail.com> wrote:<br>
><br>
> I once again contacted Radioddity Support. He installed the factory software, set it up for me and then set up Chirp for me. I have my radio programmed.<br>
> He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.<br>
><br>
> Sent from Byron Boggs<br>
> kc8ue@hotmail.com<br>
<br>
You don't need the factory software. The reason it works now is<br>
because the CHIRP daily build that was issued a couple of days ago<br>
added an additional MCU-Version (which is probably the one your radio<br>
has - VC4114). Prior to that, your radio couldn't be identified. You<br>
can verify this by looking at the following CHIRP setting...<br>
<br>
Settings -> Other Settings -> Fingerprint: {MCU-version}<br>
<br>
The MCU-Version is also displayed in the bottom status display area of<br>
the factory programming software.<br>
<br>
Jim KC9HI<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 Byron at kc8ue@hotmail.com<br>
To unsubscribe, send an email to 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/20200624/5eaa24e1/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/5eaa24e1/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Wed, 24 Jun 2020 12:36:18 -0400<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Radioddity QB25<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U4BD-2cCbD2bLmsUfos_Wj=cfP77p6Z-E+NpmuJv0XQVw@mail.gmail.com><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, Jun 24, 2020 at 11:18 AM Byron Boggs <kc8ue@hotmail.com> wrote:<br>
><br>
> Someone asked what the MCU version of my radio was. It is VC4104.<br>
><br>
> Sent from Byron Boggs<br>
> kc8ue@hotmail.com<br>
<br>
The VC4014 MCU version was added late last month. You need a CHIRP<br>
daily-200603 or later to support your radio.<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Wed, 24 Jun 2020 11:20:46 -0700<br>
From: Donald Jacob <wb5eku@gmail.com><br>
Subject: [chirp_users] unable to install<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CABCjCMCuD1k32yyncnmYn23O-9xdpAzcC2ai1EHhVyX5rv-B3A@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Windows 10 system,<br>
I tried to install daily 20200622-installer.exe<br>
and received this message. I tried running as Administrator with same<br>
results.<br>
Can't write: C:\Program Files (x86)\CHIRP\_hashlib.pyd<br>
<br>
I do have an earlier version installed, should I remove that one?<br>
If so, what will happen to my data for the older version?<br>
<br>
Thanks<br>
<br>
Don<br>
WB5EKU<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/2c05b4e0/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200624/2c05b4e0/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 138, Issue 20<br>
********************************************<br>
</div>
</span></font></div>
</body>
</html>