Project

General

Profile

Actions

Bug #11599

closed

Retevis RT98v V101 erroring as unsupported on latest release

Added by Bryant L about 2 months ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/08/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Retevis RT98v
Platform:
Linux
I read the instructions above:
Yes

Description

I am running the https://archive.chirpmyradio.com/chirp_next/next-20241003/chirp-20241003-py3-none-any.whl version of CHIRP, which was built the same day as the issue to get this model supported was resolved, #11584

I've already gone ahead and uninstalled chirp fully and reinstalled from the above link to be safe, but it is still not letting me read or write without the development module.

I went ahead and extracted the tarball and can see the supported version is also not listed in the rt98.py driver:

 ALLOWED_RADIO_TYPES = {'RT98V': ['V100'],
                           'RT98U': ['V100'],
                           'RT98W': ['V100'],
                           'AT-779V': ['V100'],
                           'AT-779U': ['V100'],
                           'AT-779W': ['V100'],
                           }

Maybe it's me, but I feel like the change just didn't get pushed out right, going to just use the dev module for now, as I already did all the testing with that one, but for the casual reader who may stumble upon this, just wait for the fix to get pushed, I don't want to misguide anyone into bricking their radios.


Related issues 1 (0 open1 closed)

Is duplicate of Bug #11593: Unable to download from radioRejected10/05/2024

Actions
Actions #1

Updated by Dan Smith about 2 months ago

  • Is duplicate of Bug #11593: Unable to download from radio added
  • Status changed from New to Rejected

The fix was merged the evening of 3-Oct, but the last build was early morning of 3-Oct, and as such, that fix is still pending a release. So yes, please keep using the module in the issue until the next release. There's no danger to "misguide anyone into bricking their radios" ... chirp was refusing to talk to the newer firmware before the fix for a reason.

Duplicate of #11593

Actions #2

Updated by Bryant L about 2 months ago

Ah okay, didn't look close enough at timestamps I guess. Figured I'd play it safe in telling people to wait, can't hurt to be safe! Appreciate all your work on this project.

Actions

Also available in: Atom PDF