New Model #10559
closedTalkpod A36plus
Added by F S over 1 year ago. Updated over 1 year ago.
100%
Description
During work on Issue 10376 [[[https://chirp.danplanet.com/issues/10376]]], Jim found there are more differences than expected between the Anysecu and the Talkpod devices. So he decided to better create a new Issu for this device.
Files
| Talkpod A36plus Menulist.txt (1.04 KB) Talkpod A36plus Menulist.txt | List of the internal Menu with some details | F S, 05/04/2023 09:53 AM | |
| mml_jc8810_a36plus_v0.2.py (44.4 KB) mml_jc8810_a36plus_v0.2.py | Jim Unroe, 05/09/2023 08:17 AM | ||
| chirp_debug-9stg8mqq.txt (4.09 KB) chirp_debug-9stg8mqq.txt | FW 1.18 debug log | David Derzsi, 05/23/2023 10:24 AM | |
| mml_jc8810_a36plus_v0.3.py (44.6 KB) mml_jc8810_a36plus_v0.3.py | add ID string for FW v1.18 and other fixes | Jim Unroe, 05/23/2023 10:51 AM | |
| Talkpod A36plus Menulist v1.18.txt (1.08 KB) Talkpod A36plus Menulist v1.18.txt | List of menu items in the v1.18 firmware | David Derzsi, 05/23/2023 11:25 AM | |
| mml_jc8810_a36plus_v0.4.py (46.2 KB) mml_jc8810_a36plus_v0.4.py | PF keys updated to fw v1.18 | Jim Unroe, 06/08/2023 10:04 AM | |
| mml_jc8810_a36plus_v0.4.1.py (46.2 KB) mml_jc8810_a36plus_v0.4.1.py | fixes some pep8 issues | Jim Unroe, 06/10/2023 05:24 PM |
Updated by Jim Unroe over 1 year ago
- Status changed from New to In Progress
- Assignee set to Jim Unroe
- Target version set to chirp-py3
Thank you for opening the ticket.
Jim
Updated by Jim Unroe over 1 year ago
- File mml_jc8810_a36plus_v0.2.py mml_jc8810_a36plus_v0.2.py added
- % Done changed from 0 to 70
I have made good progress on the Talkpod A36plus driver module. It just needs some good testing. I have attached the test driver module in its current state: mml_jc8810_a36plus_v0.2.py
Instructions for how to temporarily load and use this test driver module is available at this link: LoadingTestModules
Please test this driver module and provide your bug reports and any other feedback.
Jim KC9HI
Updated by David Derzsi over 1 year ago
Jim Unroe wrote in #note-2:
I have made good progress on the Talkpod A36plus driver module. It just needs some good testing. I have attached the test driver module in its current state: mml_jc8810_a36plus_v0.2.py
Instructions for how to temporarily load and use this test driver module is available at this link: LoadingTestModules
Please test this driver module and provide your bug reports and any other feedback.
Jim KC9HI
Hi Jim
Thanks for your work on this. Today I got my A36 plus with fw version 1.17. I tested some basic stuff like adding channels and changing some settings in CHIRP with your driver module. It was working fine with the stock FW (haven't checked every function tho). I noticed Talkpod released a new firmware (v1.18) on their site ( https://talkpodonline.com/pages/firmware-software ) so I updated it, everything went fine, did a full reset after the update from the radio menu. Now if I want to read the radio from chirp, it errors out with the message: "Radio returned unknown identification string". I guess that ID string changed with the new FW version.
Can I help somehow, is there a way I can read the new ID string from the radio?
NOTE: I'm not a programmer, only know some basic stuff and this is my first time using CHRIP with any radio :)
David
Updated by Jim Unroe over 1 year ago
David . wrote in #note-3:
Can I help somehow, is there a way I can read the new ID string from the radio?
This happened when I updated the firmware of my Radtel RT-470 from v1.15 to v1.22. The new identification string is included in the debug.log so to help all you have to do is attach you debug.log file to this issue. I will then get it from the debug.log file and add it to the driver.
Thanks,
Jim KC9HI
Updated by David Derzsi over 1 year ago
- File chirp_debug-9stg8mqq.txt chirp_debug-9stg8mqq.txt added
Jim Unroe wrote in #note-4:
David . wrote in #note-3:
Can I help somehow, is there a way I can read the new ID string from the radio?
This happened when I updated the firmware of my Radtel RT-470 from v1.15 to v1.22. The new identification string is included in the debug.log so to help all you have to do is attach you debug.log file to this issue. I will then get it from the debug.log file and add it to the driver.
Thanks,
Jim KC9HI
ok, the debug log is attached. thanks
Updated by Jim Unroe over 1 year ago
David . wrote in #note-5:
Jim Unroe wrote in #note-4:
David . wrote in #note-3:
Can I help somehow, is there a way I can read the new ID string from the radio?
This happened when I updated the firmware of my Radtel RT-470 from v1.15 to v1.22. The new identification string is included in the debug.log so to help all you have to do is attach you debug.log file to this issue. I will then get it from the debug.log file and add it to the driver.
Thanks,
Jim KC9HIok, the debug log is attached. thanks
Test driver v0.3 added.
Would you download the attached menu list (Talkpod A36plus Menulist.txt) and compare it to your radio with v1.18 firmware? If there are any differences please update the list accordingly, add v1.18 to the list's filename and attach the new list to this issue. Thanks.
Jim KC9HI
Updated by David Derzsi over 1 year ago
Jim Unroe wrote in #note-6:
David . wrote in #note-5:
Jim Unroe wrote in #note-4:
David . wrote in #note-3:
Can I help somehow, is there a way I can read the new ID string from the radio?
This happened when I updated the firmware of my Radtel RT-470 from v1.15 to v1.22. The new identification string is included in the debug.log so to help all you have to do is attach you debug.log file to this issue. I will then get it from the debug.log file and add it to the driver.
Thanks,
Jim KC9HIok, the debug log is attached. thanks
Test driver v0.3 added.
Would you download the attached menu list (Talkpod A36plus Menulist.txt) and compare it to your radio with v1.18 firmware? If there are any differences please update the list accordingly, add v1.18 to the list's filename and attach the new list to this issue. Thanks.
Jim KC9HI
I tested the v0.3 driver, it reads and can write the radio too. The main menu is identical to v1.17, there are some extra entries in the button function menus (Remote Scan for 40,42,43 and DTMF for 41), added those to the v1.18 menulist file.
Updated by Jim Unroe over 1 year ago
David Derzsi wrote in #note-7:
I tested the v0.3 driver, it reads and can write the radio too. The main menu is identical to v1.17, there are some extra entries in the button function menus (Remote Scan for 40,42,43 and DTMF for 41), added those to the v1.18 menulist file.
Hi David,
I need a CHIRP image with at least one of the PF Keys manually set to Remote Scan using the radio's menu system.
Thanks,
Jim
Updated by Jim Unroe over 1 year ago
- File mml_jc8810_a36plus_v0.4.py mml_jc8810_a36plus_v0.4.py added
- % Done changed from 70 to 90
This test driver module updates the PF keys to support the changes brought about by firmware v1.18 update. Please test and provide feedback. Unless there are problems found, this is likely to be the what I submit.
Jim KC9HI
Updated by Jim Unroe over 1 year ago
Add v0.4.1 which fixes some pep8 issues.
Jim
Updated by Anonymous over 1 year ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Applied in changeset github|f97c66edbdd7c8e25e8507757b75ef91bb623d41.