New Model #9806: Chirp support for Radioddity GS-5B? - CHIRP

Custom queries

All CHIRP-next Bugs
All CHIRP-next Feature Requests
All closed issues
All open issues
New Model Requests
Open bugs by Developer
Open bugs by Target Version
Potentially Stalled Bugs

New Model #9806

closed

Chirp support for Radioddity GS-5B?

Added by Michael Chiu over 2 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

03/27/2022

Due date:

% Done:

Estimated time:

Equipment Loan/Gift Offered:

I read the instructions above:

Description

I recently acquired a Radioddity GS-5B unit. I would like to use Chirp to program it, as Radioddity is an all-Windows brand while I currently do not have Windows OS. It appears that official Chirp support for GS-5B was fairly close a year ago, but somehow stalled. See the Model thread here: https://chirp.danplanet.com/issues/9643. I didn't want to make a "new model" thread for this issue. Any status updates or help on how Chirp may be used for my unit? Thanks in advance.

Related issues 1 (0 open — 1 closed)

Is duplicate of New Model #7997: Radioddity gs-5b

Closed

06/19/2020

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Michael Chiu over 2 years ago

I posted an incorrect thread link. Here's the correct one: https://chirp.danplanet.com/issues/7997. Updates or help appreciated.

Actions

Copy link

Updated by Michael Chiu over 2 years ago

Also, the 'Chirp-daily' build itself seems to be lacking more recent or regular updates for both WindowsOS and MacOS. Not sure--is this possible indicating factor for the slow model adoption? What gives?

Actions

Copy link

Updated by Jim Unroe over 2 years ago

Status changed from New to Feedback

Michael Chiu wrote:

Also, the 'Chirp-daily' build itself seems to be lacking more recent or regular updates for both WindowsOS and MacOS. Not sure--is this possible indicating factor for the slow model adoption? What gives?

When the process runs to create a new CHIRP daily build, it creates builds for all of the supported operating systems: Windows, Linux and macOS. All builds having the same build date will always have support for the exact same list of radios.

The build process is only triggered when it has been deemed that a large enough change and/or sufficient number among the patches have been submitted.

Some radio drivers require that the python-future module has been installed. Without it, those radios will not be listed. The Windows build comes with the python-future module preinstalled. For Linux and macOS, the user must install this dependency manually if support for this small list of radios is required.

Jim KC9HI

Actions

Copy link

Updated by Michael Chiu over 2 years ago

OK, thanks for the reply. Jim, can you confirm then that Radioddity GS-5B has not moved to adoption is lack of patches or builds? Seems a bit of a stretch for a unit almost 2 years old with a strong showing within the community at large.

Actions

Copy link

Updated by Jim Unroe over 2 years ago

Michael Chiu wrote:

OK, thanks for the reply. Jim, can you confirm then that Radioddity GS-5B has not moved to adoption is lack of patches or builds? Seems a bit of a stretch for a unit almost 2 years old with a strong showing within the community at large.

You need to understand that these drivers can take quite a bit of effort to reverse engineer. One driver took me 3 months (working evenings, weekends and 2 vacation weeks). They are also created by volunteer developers. They shouldn't be expected to go out an purchase a radio out of their own pocket just to satisfy a person that has requested a radio.

In my case, I normally will only consider doing this work if a radio (and compatible programming cable) is donated with no strings attached. I have had several radios donated by vendors wishing to have their radio supported by CHIRP. A few individual have done the same. But having access to the radio is no guarantee of CHIRP support. I have a few donated radios that I have not been able to get reverse engineered in order to create the driver.

Jim KC9HI

Actions

Copy link