Project

General

Profile

Actions

Bug #10572

closed

Radtel RT-470 cant read Radio - FW1.22

Added by Johnny RT470Owner 10 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/12/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Radtel RT-470
Platform:
Windows
I read the instructions above:

Description

Got mine updated to Firmware V1.22. Its not reading the radio anymore.


Files

chirp_debug-0z4490hg.txt (2.05 KB) chirp_debug-0z4490hg.txt Johnny RT470Owner, 05/13/2023 07:49 AM
IMG_20230513_171608.jpg (499 KB) IMG_20230513_171608.jpg Johnny RT470Owner, 05/13/2023 08:23 AM
IMG_20230513_171743.jpg (544 KB) IMG_20230513_171743.jpg Johnny RT470Owner, 05/13/2023 08:23 AM
mml_jc8810_0000004a0020f804.py (40.3 KB) mml_jc8810_0000004a0020f804.py Jim Unroe, 05/13/2023 09:30 AM
Actions #1

Updated by Jim Unroe 10 months ago

Johnny RT470Owner wrote:

Got mine updated to Firmware V1.22. Its not reading the radio anymore.

This doesn't appear to be a recent debug.log file. It says the current CHIRP-next version is 20230411 which was over a month ago.

Jim

Actions #2

Updated by Johnny RT470Owner 10 months ago

My fault, selected the wrong debug file. Here's the actual logfile.

Actions #3

Updated by Jim Unroe 10 months ago

Johnny RT470Owner wrote in #note-2:

My fault, selected the wrong debug file. Here's the actual logfile.

I looks the identification string has changed to one that is unknown by CHIRP. Please verify that you have an RT-470 and not an RT-470L. Also, what is the range of menu selections (00-52, 00-54, 00-56, etc)?

Jim KC9HI

Actions #4

Updated by Johnny RT470Owner 10 months ago

It's a RT-470. Last menu is 51 as shown in the picture.

Actions #5

Updated by Jim Unroe 10 months ago

  • Status changed from New to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-py3

Johnny RT470Owner wrote in #note-4:

It's a RT-470. Last menu is 51 as shown in the picture.

Thanks. I wanted to make sure there weren't any new menus that needed to be accounted for.

After lunch, I will see about adding a test driver module to this issue for you to test.

Are you able to share where you got the firmware update?

Jim KC9HI

Actions #6

Updated by Johnny RT470Owner 10 months ago

Yeah i worte Kevin from Radtel if theres a firmware update and he send me a flashing tool.
I had an issue with my TX power shown on the display and the update fixed that. So im on 1.22 now.
I dunno if im allowed to share the files that Kevin provided me.

Actions #7

Updated by Jim Unroe 10 months ago

Johnny RT470Owner wrote in #note-6:

Yeah i worte Kevin from Radtel if theres a firmware update and he send me a flashing tool.
I had an issue with my TX power shown on the display and the update fixed that. So im on 1.22 now.
I dunno if im allowed to share the files that Kevin provided me.

Would it be possible for you to send Mr. Xie's email address to me? I have his WhatsApp number but I would rather email him. If that is possible, you can email it to: jru.chirp@kc9hi.net

I have attached the test driver module that should allow CHIRP to recognize your radio's identification string. Instructions for using this driver module is available here: LoadingTestModules

Once I get positive feedback from you, I will try to create and submit a patch to add this additional identification to CHIRP.

Jim KC9HI

Actions #8

Updated by Johnny RT470Owner 10 months ago

I was able to read my radio with this test driver :)

Actions #9

Updated by Jim Unroe 10 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Johnny RT470Owner wrote in #note-8:

I was able to read my radio with this test driver :)

A patch has been submitted. Support will be in the next CHIRP build following acceptance.

Jim KC9HI

Actions #10

Updated by MELERIX . 9 months ago

sorry for a bit off-topic guy, but do you have a copy of firmware 1.22? because I've upgraded to 1.23 and now my radio does not receive anything unless is really near to it, so maybe downgrading to 1.22 could solve the issue?

Actions #11

Updated by Jim Unroe 9 months ago

MELERIX . wrote in #note-10:

sorry for a bit off-topic guy, but do you have a copy of firmware 1.22? because I've upgraded to 1.23 and now my radio does not receive anything unless is really near to it, so maybe downgrading to 1.22 could solve the issue?

I just updated to 1.23A which was recently added to the Radtel download page. It worked for me, receive appears to be normal and restored my "dead" VHF and 330-400 MHz bands.

Jim KC9HI

Actions #12

Updated by Jim Unroe 9 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF