[chirp_users] Radioddity QB25
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Sent from Byron Boggs kc8ue@hotmail.com
On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs kc8ue@hotmail.com wrote:
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Hi Byron,
Your QB25 most likely has an MCU-Version that is not recognized by CHIRP. I recently submitted a patch to add one in May (VC4114) and another one in June (VC4104) but the most recent one hasn't been accepted yet. There are quite a few patches in the queue to be accepted but the process has been slowed down by the Covid-19 pandemic. Unless it has an even different MCU-Version than the one I just added, it will be supported in the next CHIRP daily build. You can determine the MCU-Version using the factory programming software. It will be shown in the bottom status display area.
Jim KC9HI
I don't have the factory software. My xyl threw the shipping box out and the disk was in it. Don't know how to obtain the version. I tried to download the software from the internet without success.
Sent from Byron Boggs kc8ue@hotmail.com ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Jim Unroe rock.unroe@gmail.com Sent: Friday, June 19, 2020 2:00:19 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] Radioddity QB25
On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs kc8ue@hotmail.com wrote:
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Hi Byron,
Your QB25 most likely has an MCU-Version that is not recognized by CHIRP. I recently submitted a patch to add one in May (VC4114) and another one in June (VC4104) but the most recent one hasn't been accepted yet. There are quite a few patches in the queue to be accepted but the process has been slowed down by the Covid-19 pandemic. Unless it has an even different MCU-Version than the one I just added, it will be supported in the next CHIRP daily build. You can determine the MCU-Version using the factory programming software. It will be shown in the bottom status display area.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Byron at kc8ue@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Radioddity website.
On 19 June 2020 at 14:49 Byron Boggs kc8ue@hotmail.com wrote:
I don't have the factory software. My xyl threw the shipping box out and the disk was in it. Don't know how to obtain the version. I tried to download the software from the internet without success. Sent from Byron Boggs kc8ue@hotmail.com --------------------------------------------- .
I just sent Byron a copy of the zip file of the software.
73 David N1EA
On Fri, Jun 19, 2020 at 2:56 PM Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
Radioddity website.
On 19 June 2020 at 14:49 Byron Boggs kc8ue@hotmail.com wrote:
I don't have the factory software. My xyl threw the shipping box out and the disk was in it. Don't know how to obtain the version. I tried to download the software from the internet without success.
Sent from Byron Boggs kc8ue@hotmail.com
*.*
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Fri, Jun 19, 2020 at 2:52 PM Byron Boggs kc8ue@hotmail.com wrote:
I don't have the factory software. My xyl threw the shipping box out and the disk was in it. Don't know how to obtain the version. I tried to download the software from the internet without success.
Sent from Byron Boggs kc8ue@hotmail.com
I just downloaded the programming software and user's manual without any problem.
Jim KC9HI
On Fri, Jun 19, 2020 at 2:00 PM Jim Unroe rock.unroe@gmail.com wrote:
On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs kc8ue@hotmail.com wrote:
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Hi Byron,
Your QB25 most likely has an MCU-Version that is not recognized by CHIRP. I recently submitted a patch to add one in May (VC4114) and another one in June (VC4104) but the most recent one hasn't been accepted yet. There are quite a few patches in the queue to be accepted but the process has been slowed down by the Covid-19 pandemic. Unless it has an even different MCU-Version than the one I just added, it will be supported in the next CHIRP daily build. You can determine the MCU-Version using the factory programming software. It will be shown in the bottom status display area.
Jim KC9HI
Assuming that your radio's MCU-version is VC4114, today's CHIRP daily build should allow it to be recognized.
Jim KC9HI
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. He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.
Sent from Byron Boggs kc8ue@hotmail.com
________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Jim Unroe rock.unroe@gmail.com Sent: Monday, June 22, 2020 10:53:22 AM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] Radioddity QB25
On Fri, Jun 19, 2020 at 2:00 PM Jim Unroe rock.unroe@gmail.com wrote:
On Fri, Jun 19, 2020 at 1:23 PM Byron Boggs kc8ue@hotmail.com wrote:
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Hi Byron,
Your QB25 most likely has an MCU-Version that is not recognized by CHIRP. I recently submitted a patch to add one in May (VC4114) and another one in June (VC4104) but the most recent one hasn't been accepted yet. There are quite a few patches in the queue to be accepted but the process has been slowed down by the Covid-19 pandemic. Unless it has an even different MCU-Version than the one I just added, it will be supported in the next CHIRP daily build. You can determine the MCU-Version using the factory programming software. It will be shown in the bottom status display area.
Jim KC9HI
Assuming that your radio's MCU-version is VC4114, today's CHIRP daily build should allow it to be recognized.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Byron at kc8ue@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs kc8ue@hotmail.com wrote:
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. He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.
Sent from Byron Boggs kc8ue@hotmail.com
You don't need the factory software. The reason it works now is because the CHIRP daily build that was issued a couple of days ago added an additional MCU-Version (which is probably the one your radio has - VC4114). Prior to that, your radio couldn't be identified. You can verify this by looking at the following CHIRP setting...
Settings -> Other Settings -> Fingerprint: {MCU-version}
The MCU-Version is also displayed in the bottom status display area of the factory programming software.
Jim KC9HI
Someone asked what the MCU version of my radio was. It is VC4104.
Sent from Byron Boggs kc8ue@hotmail.com ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Jim Unroe rock.unroe@gmail.com Sent: Wednesday, June 24, 2020 10:47:24 AM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] Radioddity QB25
On Wed, Jun 24, 2020 at 10:05 AM Byron Boggs kc8ue@hotmail.com wrote:
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. He said to open the factory software first, then open Chirp as the Administrator and it works. I does work.
Sent from Byron Boggs kc8ue@hotmail.com
You don't need the factory software. The reason it works now is because the CHIRP daily build that was issued a couple of days ago added an additional MCU-Version (which is probably the one your radio has - VC4114). Prior to that, your radio couldn't be identified. You can verify this by looking at the following CHIRP setting...
Settings -> Other Settings -> Fingerprint: {MCU-version}
The MCU-Version is also displayed in the bottom status display area of the factory programming software.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Byron at kc8ue@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jun 24, 2020 at 11:18 AM Byron Boggs kc8ue@hotmail.com wrote:
Someone asked what the MCU version of my radio was. It is VC4104.
Sent from Byron Boggs kc8ue@hotmail.com
The VC4014 MCU version was added late last month. You need a CHIRP daily-200603 or later to support your radio.
Jim KC9HI
Byron, I ended up purchasing the DB25 instead of the quad band (QB25) radio. In the setup for programming using Chirp I had to use the QTY brand and selecting the 7200D or 7800D. I can't remember correctly and I'm not at my computer to tell you for sure but I think one of those was the model number. I haven't used the supplied software but I am going to try it tonight and look at the differences.
I hope this helps. Please post your route of success if you would.
73' and best if luck.
Rick W7NGS
On Fri, Jun 19, 2020, 10:22 AM Byron Boggs kc8ue@hotmail.com wrote:
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. 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. Suggestions will be greatly appreciated
Byron Kc8ue
Sent from Byron Boggs kc8ue@hotmail.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to KD6GJS at richard.cooper38@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (5)
-
Byron Boggs -
D.J.J. Ring, Jr. -
Jim Unroe -
Nigel A. Gunn G8IFF/W8IFF -
Rick Cooper