Bug #11928
openRadtel RT-620 Memory Size doesn't Match
Added by Darik Boutsaboualoy 10 days ago. Updated 1 day ago.
0%
Description
(Describe what you were doing)
I was trying to download from the radio into Chirp.
(Describe what you expected to happen)
I expected a full list of frequencies already on the radio to be populated into Chirp to begin modifying the settings
(Describe what actually happened instead)
An immediate error message appeared: "Incorrect radio model or model not supported (memory size doesn't match)."
(Has this ever worked before? New radio? Does it work with OEM software?)
This has never worked before, but I saw that RT-620 was an added model to Chirp's list of supported radios. It isn't necessarily a new radio on the market. It does work with OEM software, however not user friendly with copy/paste features, etc. that Chirp has.
Files
| config.txt (2.69 KB) config.txt | Darik Boutsaboualoy, 04/09/2025 08:03 PM | ||
| win_system_info.txt (68.2 KB) win_system_info.txt | Darik Boutsaboualoy, 04/09/2025 08:03 PM | ||
| debug_log.txt (5.72 KB) debug_log.txt | Darik Boutsaboualoy, 04/09/2025 08:03 PM | ||
| chirp_debug-bn83eghk.txt (6.81 KB) chirp_debug-bn83eghk.txt | Darik Boutsaboualoy, 04/09/2025 08:07 PM | ||
| baofeng_uv17.py (15.2 KB) baofeng_uv17.py | Dan Smith, 04/09/2025 08:12 PM | ||
| radtel_rt620.py (14.7 KB) radtel_rt620.py | Dan Smith, 04/09/2025 08:12 PM | ||
| config.txt (2.69 KB) config.txt | Darik Boutsaboualoy, 04/10/2025 11:31 AM | ||
| win_system_info.txt (68.2 KB) win_system_info.txt | Darik Boutsaboualoy, 04/10/2025 11:31 AM | ||
| debug_log.txt (7.57 KB) debug_log.txt | Darik Boutsaboualoy, 04/10/2025 11:31 AM | ||
| test-module.py (29.9 KB) test-module.py | Dan Smith, 04/11/2025 04:37 AM | ||
| config.txt (2.93 KB) config.txt | Darik Boutsaboualoy, 04/11/2025 05:05 PM | ||
| win_system_info.txt (68.2 KB) win_system_info.txt | Darik Boutsaboualoy, 04/11/2025 05:05 PM | ||
| debug_log.txt (7.35 KB) debug_log.txt | Darik Boutsaboualoy, 04/11/2025 05:05 PM | ||
| radtel_rt620.py (14.9 KB) radtel_rt620.py | Old V01.00.030 firmware support | Pavel Moravec, 04/11/2025 10:36 PM | |
| config.txt (2.85 KB) config.txt | Darik Boutsaboualoy, 04/12/2025 08:47 PM | ||
| win_system_info.txt (68.2 KB) win_system_info.txt | Darik Boutsaboualoy, 04/12/2025 08:47 PM | ||
| debug_log.txt (10.8 KB) debug_log.txt | Darik Boutsaboualoy, 04/12/2025 08:47 PM | ||
| config.txt (3.36 KB) config.txt | Darik Boutsaboualoy, 04/18/2025 07:05 AM | ||
| Radtel_RT-620-V01.00.030_20250418.img (40.2 KB) Radtel_RT-620-V01.00.030_20250418.img | Darik Boutsaboualoy, 04/18/2025 07:05 AM | ||
| win_system_info.txt (69.3 KB) win_system_info.txt | Darik Boutsaboualoy, 04/18/2025 07:05 AM | ||
| debug_log.txt (361 KB) debug_log.txt | Darik Boutsaboualoy, 04/18/2025 07:05 AM |
Updated by Darik Boutsaboualoy 10 days ago
- File config.txt config.txt added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250404]
Updated by Darik Boutsaboualoy 10 days ago
- File chirp_debug-bn83eghk.txt chirp_debug-bn83eghk.txt added
Debug Log Attached for RT-620 ""Incorrect radio model or model not supported (memory size doesn't match).""Incorrect radio model or model not supported (memory size doesn't match)."
Updated by Dan Smith 10 days ago
@Pavel Moravec Any ideas here? Looks like we don't log the thing we're getting and rejecting from the radio.
Updated by Dan Smith 10 days ago
- File baofeng_uv17.py baofeng_uv17.py added
- File radtel_rt620.py radtel_rt620.py added
Darik, please try loading these modules (in order) using this procedure LoadingTestModules. You need to load the baofeng one first, then the radtel one. Then try to reproduce the problem (the error will be the same) and then use Help->Report or update a bug to update this bug with a new debug log after you try. I'm trying to collect some more information, this won't fix the problem.
Updated by Pavel Moravec 10 days ago
I will look into it, as I am the author of the driver, but this message indicates different reported size of built-in memory than what is expected. One of the possibilities I can think of is that non-GPS version which I don't have reports different size. Do you have GPS or non-GPS version?
The second possibility is that something has changed in hardware/firmware as these radios are prone to unanounced changes.
Updated by Darik Boutsaboualoy 10 days ago
- File config.txt config.txt added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250404]
(Describe what you were doing)
Darik, please try loading these modules (in order) using this procedure LoadingTestModules. You need to load the baofeng one first, then the radtel one. Then try to reproduce the problem (the error will be the same) and then use Help->Report or update a bug to update this bug with a new debug log after you try. I'm trying to collect some more information, this won't fix the problem.
(Describe what you expected to happen)
(Describe what actually happened instead)
(Has this ever worked before? New radio? Does it work with OEM software?)
Additional questions to answer from previous replies from Pavel and Dan:
(Do you have GPS or non-GPS version?) >> Yes, my Radtel RT-620 DOES have GPS function on it. Never used it however. I also never udpated any hardware/firmware on the radio. I got the radio from Radtel's website.
Updated by Pavel Moravec 9 days ago · Edited
Unfortunately as far as I can tell from the logs, the (wrong) size is still not logged. I could disable the check in the driver, and upload it here, but it could be risky.
Can you let me know what is the firmware version reported by the radio when you look at it in the menu?
EDIT: Mine is the latest firmware I was able to obtain from Radtel several months ago, which is V01.01.040/D1.01.01.004/S1.00.01.001
Updated by Dan Smith 9 days ago
- File test-module.py test-module.py added
Darik, here's another module to try. This will hopefully get us the data we're looking for. Just load this one into a clean chirp and then try to reproduce for us. Thanks for your patience.
Pavel, agree that disabling the memory size check is risky. Early on in the development of that driver the original author got it wrong for the UV-13 and we had an angry mob thinking their radios had been bricked. We worked it out, but let's not have that again :)
Updated by Darik Boutsaboualoy 9 days ago
- File config.txt config.txt added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250404]
(Describe what you were doing)
Loaded file from Dan Smith "test-module.py" and tried to download from radio to recreate the problem as instructed.
(Describe what you expected to happen)
(Describe what actually happened instead)
(Has this ever worked before? New radio? Does it work with OEM software?)
(Radio Info, Firmware Version)
"V01.00.030" Do I need to request new firmware from Radtel?
Updated by Pavel Moravec 8 days ago · Edited
- File radtel_rt620.py radtel_rt620.py added
This driver takes your different reported memory size into account, a new model is created due to the way how the memory size is handled in class from which I inherit. I think it should be possible to share the new firmware with you (on the other hand, "if it is not broken, don't fix" it comes to my mind).
I can't, however, ensure, that all functionality will be available in this older firmware, i.e. some settings may not have any impact. Channel edits should work if you are using CPS from Radtel web and it does not break anything in radio, but I would suggest you back up the settings in official application first just in case.
Updated by Darik Boutsaboualoy 7 days ago
- File config.txt config.txt added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250404]
(Describe what you were doing)
I loaded the module from Pavel that was supposed to take my reported memory into account but I still received the same error.
(Describe what you expected to happen)
I expected the memory issue to go away since it was mentioned the new module was taking into account my reported memory size.
(Describe what actually happened instead)
Same issue happened again.
(Has this ever worked before? New radio? Does it work with OEM software?)
Are there any other details you would like about my RT-620 to solve the issue?
Updated by Pavel Moravec 2 days ago
I think you did not use the special driver variant (Radtel RT-620 (old firmware)) when testing based on the logs you have supplied. Unfortunately, the base driver from which the original RT-620 one is inherited does not support multiple memory sizes, so there can be only one per driver.
Updated by Darik Boutsaboualoy 2 days ago
- File config.txt config.txt added
- File Radtel_RT-620-V01.00.030_20250418.img Radtel_RT-620-V01.00.030_20250418.img added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250404]
(Describe what you were doing)
Pavel mentioned I did not use the special driver variant for the 'old firmware', even though I thought I did? I decided to try again and loaded the module (the file name was the same as a previous one, so I must have gotten it mixed up).
(Describe what you expected to happen)
I expected the download from Radio to happen
(Describe what actually happened instead)
Chirp did successfully download from the radio and looks like I have the ability now to edit frequencies and settings on the Radtel RT-620!
(Has this ever worked before? New radio? Does it work with OEM software?)
It now seems to work, I appreciate all the time and efforts from Dan and Pavel. I will play around with this and let you know if there are any issues, right now it seems to be working!