Bug #11005
closedSettings tab fails to render when using ft1d driver
0%
Description
This is similar but not identical to #10628. Apologies for lack of debug log as the instructions say I can get it from the Help menu in chirp-next but this is not the case (maybe the menu option was moved or removed?).
As in the aforementioned issue, after cloning my radio (FT3D), I attempt to open the Settings tab, but instead get an error pop-up and the settings pane is not rendered. However, my stack trace indicates that a different setting is the culprit than that of the other issue.
Here is the stack trace I can see in the console when this error occurs:
ERROR: Failed to parse settings: Traceback (most recent call last):
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/drivers/ft1d.py", line 2336, in get_settings
return self._get_settings()
^^^^^^^^^^^^^^^^^^^^
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/drivers/ft1d.py", line 2327, in _get_settings
self._get_digital_settings(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/drivers/ft1d.py", line 1837, in _get_digital_settings
self._AMS_TX_MODE[digital_settings.ams_tx_mode])
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
IndexError: tuple index out of range
ERROR: Context raised unexpected_exception
Traceback (most recent call last):
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/wxui/settingsedit.py", line 51, in _initialize
self._load_settings()
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/wxui/settingsedit.py", line 81, in _load_settings
for group in self._settings:
TypeError: 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/wx/core.py", line 3427, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/wxui/settingsedit.py", line 51, in _initialize
self._load_settings()
File "/home/david/.local/pipx/venvs/chirp/lib/python3.11/site-packages/chirp/wxui/settingsedit.py", line 81, in _load_settings
for group in self._settings:
TypeError: 'NoneType' object is not iterable
I am running the latest available chirp-next as of today (20231209).
Files
| Open-debug-log_on_Linux_Mint.png (337 KB) Open-debug-log_on_Linux_Mint.png | |||
| chirp_debug-lr6n2w21.txt (911 Bytes) chirp_debug-lr6n2w21.txt | |||
| 2023-12-11-182132_1920x1080_scrot.png (159 KB) 2023-12-11-182132_1920x1080_scrot.png | Help menu without debug log option | ||
| Yaesu_FT3D_20231211.img (128 KB) Yaesu_FT3D_20231211.img | |||
| Yaesu_FT3D_20231211(aws_tx_mode_auto).img (128 KB) Yaesu_FT3D_20231211(aws_tx_mode_auto).img |
Updated by Jim Unroe 5 months ago
- File Open-debug-log_on_Linux_Mint.png Open-debug-log_on_Linux_Mint.png added
- File chirp_debug-lr6n2w21.txt chirp_debug-lr6n2w21.txt added
You are the 2nd person in as many days that claims the 'Open debug log' option is missing. So just to make sure that something didn't get changed by accident, I upgraded my Linux Mint that I have running from a USB stick to the latest build and looked to see. It is there just as it is expected to be (see screen capture) and if I click it, the debug log shows up in a text editor (attached).
If you still can't find it, at least attach your downloaded CHIRP Radio Images (*.img) file so a developer can use it replicate the error and look at their local debug log file.
Updated by David McMackins 5 months ago
- File 2023-12-11-182132_1920x1080_scrot.png 2023-12-11-182132_1920x1080_scrot.png added
- File Yaesu_FT3D_20231211.img Yaesu_FT3D_20231211.img added
Are you running from the source tree or the .whl available from the download link? Something is clearly different. I've attached a screenshot of my own and my image file.
Updated by Jim Unroe 5 months ago
David McMackins wrote in #note-2:
Are you running from the source tree or the .whl available from the download link? Something is clearly different. I've attached a screenshot of my own and my image file.
I installed CHIRP-next by following the instructions on the 'Running CHIRP on Linux' page. So that would be from the .whl.
Updated by Jim Unroe 5 months ago
CHIRP doesn't know how to handle the AMS TX Mode setting in your radio. CHIRP understands 3 settings choices, 0 "TX Auto", 1 "TX DIGITAL" and 2 "TX FM" but the value in your image is 3. Try changing this setting in your radio to the other values to see if that changed the value to one of the values that CHIRP understands.
And if that doesn't work (it should), I changed the value to 0 (auto) in the image that you supplied and that worked for me.
Updated by David McMackins 5 months ago
Do you mind telling me where that setting is? I know how to set the mode and override AMS at the VFO, but if this is a setting in the menu, I can't find it.
Updated by David McMackins 5 months ago
In a classic case of asking a moment too soon, I found it. The center button when in AMS mode. That did the trick. Not sure how it got that extra value in there, but all good.
Updated by Jim Unroe 5 months ago
- Status changed from New to Resolved
David McMackins wrote in #note-6:
In a classic case of asking a moment too soon, I found it. The center button when in AMS mode. That did the trick. Not sure how it got that extra value in there, but all good.
Yeah. I'm just going by what I see in the driver. I've never had or used any Yaesu radios. I am happy to see that you have it working now.