Bug #11624
closedIt still works. Please allow VX-177 which also did read, but can't edit or write
Added by Pres Waterman 8 months ago. Updated 8 months ago.
100%
Description
(Describe what you were doing)
I used CHIRP to read my old VX-177 which DID work but...
(Describe what you expected to happen)
Since it read, I would think it would edit or write but...
(Describe what actually happened instead)
The UHF frequencies obviously won't work in the VHF program, but they could...
(Has this ever worked before? New radio? Does it work with OEM software?)
The VX-177 works with OEM (made by RT Systems). Since the VX-170 works in CHIRP it would be nice if it weren't prevented from working by a band limit.
THANK YOU!
Files
config.txt (1.58 KB) config.txt | Pres Waterman, 10/20/2024 11:05 AM | ||
Yaesu_VX-170_20241020.img (6.1 KB) Yaesu_VX-170_20241020.img | Pres Waterman, 10/20/2024 11:05 AM | ||
debug_log.txt (17.9 KB) debug_log.txt | Pres Waterman, 10/20/2024 11:05 AM | ||
config.txt (1.7 KB) config.txt | Pres Waterman, 10/21/2024 02:23 PM | ||
Yaesu_VX-170_20241021.img (6.1 KB) Yaesu_VX-170_20241021.img | Pres Waterman, 10/21/2024 02:23 PM | ||
debug_log.txt (534 KB) debug_log.txt | Pres Waterman, 10/21/2024 02:23 PM | ||
vx170.py (3.86 KB) vx170.py | Dan Smith, 10/21/2024 03:09 PM | ||
config.txt (1.67 KB) config.txt | Pres Waterman, 10/21/2024 04:23 PM | ||
Yaesu_VX-170_20241021.img (6.1 KB) Yaesu_VX-170_20241021.img | Pres Waterman, 10/21/2024 04:23 PM | ||
debug_log.txt (9.08 KB) debug_log.txt | Pres Waterman, 10/21/2024 04:23 PM | ||
image.png (280 KB) image.png | Pres Waterman, 10/21/2024 05:03 PM | ||
config.txt (1.8 KB) config.txt | Pres Waterman, 10/22/2024 06:40 PM | ||
Yaesu_VX-177_20241022-1.img (6.1 KB) Yaesu_VX-177_20241022-1.img | Pres Waterman, 10/22/2024 06:40 PM | ||
debug_log.txt (60.1 KB) debug_log.txt | Pres Waterman, 10/22/2024 06:40 PM | ||
vx170.py (4.24 KB) vx170.py | Dan Smith, 10/22/2024 06:50 PM | ||
config.txt (1.79 KB) config.txt | Pres Waterman, 10/22/2024 07:29 PM | ||
Yaesu_VX-177_20241022-2.img (6.1 KB) Yaesu_VX-177_20241022-2.img | Pres Waterman, 10/22/2024 07:29 PM | ||
debug_log.txt (70.4 KB) debug_log.txt | Pres Waterman, 10/22/2024 07:29 PM |
Updated by Pres Waterman 8 months ago
- File config.txt config.txt added
- File Yaesu_VX-170_20241020.img Yaesu_VX-170_20241020.img added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241014]
Updated by Dan Smith 8 months ago
I'm pretty confused about what you're asking. Are you saying the image you attached is actually from a VX-177 and all the frequencies in the radio are actually UHF? If so, please tell me what the first few frequencies in the radio are supposed to be. This radio does not store the actual frequency used, but rather a multiple so CHIRP doesn't actually know what is intended here.
Also, are you saying you've tried to upload this (unchanged) to the radio and it fails or what?
Updated by Pres Waterman 8 months ago
Hi Dan.
Executive summary:
VX-170 (2m) reads and writes fine. VX-177 reads when set as a VX-170, but
cannot upload/write or edit, as the UHF frequencies are illegal for the
specified radio (VX-170).
QUESTION 1
VX-170 (2m) is on the list of radios supported. Its brother VX-177 (UHF) is
not. Your notes say VX-170 WAS supported but you're not sure if it is still
good, and to submit a bug report to confirm. VX-170 does work. Having
nothing to lose, I tried reading the VX-177 (UHF) as a VX-170 (VHF). That
worked! However, the frequencies it read (UHF) were not valid for the VHF
file. I can't re-upload them, and I can't edit them, because the program
flags them as illicit frequencies.
SUGGESTION 1
Perhaps it's nothing more than declaring VX-177 works, and setting the
valid frequencies for VX-177 to 420-450MHz.
SUGGESTION 2
Because many radios at least receive out of ham bands, could you have an "I
get it, but I still want to program this nonetheless" option?
QUESTION 2
Understanding that each radio has different supported features, is it
possible to clone one radio file to another with the least common
denominator features carried over? At this point I think one has to read a
radio, then edit, but at the upload stage the model choice is grayed out. I
have a STUPID number of HTs and I would like to have them all programmed
alike without typing the file over and over.
By the way, you gave an in-person talk to Great South Bay Radio Club (Long
Island, NY) a few years ago. We really enjoyed it and would love to do a
repeat, plus another one for Suffolk County Radio Club. Are you interested?
Zoom is fine if you're not local.
Thanks
-Pres W2PW
On Sun, Oct 20, 2024 at 2:09 PM Dan Smith redmine@chirpmyradio.com wrote:
Updated by Dan Smith 8 months ago
VX-170 (2m) reads and writes fine. VX-177 reads when set as a VX-170, but
cannot upload/write or edit, as the UHF frequencies are illegal for the
specified radio (VX-170).VX-170 (2m) is on the list of radios supported. Its brother VX-177 (UHF) is
not. Your notes say VX-170 WAS supported but you're not sure if it is still
good, and to submit a bug report to confirm. VX-170 does work.
You're referring to the asterisk on the front page about the VX-170? If so, thanks, I'll update.
SUGGESTION 1
Perhaps it's nothing more than declaring VX-177 works, and setting the
valid frequencies for VX-177 to 420-450MHz.
No, it's not that simple. As I asked, please download from the VX-177, try to immediately re-upload the same thing to the radio (without making changes), and then use the report-or-update tool to send the debug log and image that you get from the VX-177 here so I can look at it along with the debug log.
SUGGESTION 2
Because many radios at least receive out of ham bands, could you have an "I
get it, but I still want to program this nonetheless" option?
No, it's not that simple, especially for this radio because it does not even store the frequency as you see it.
QUESTION 2
Understanding that each radio has different supported features, is it
possible to clone one radio file to another with the least common
denominator features carried over? At this point I think one has to read a
radio, then edit, but at the upload stage the model choice is grayed out. I
have a STUPID number of HTs and I would like to have them all programmed
alike without typing the file over and over.
You can copy and paste (or import) between them, as you have been able to with CHIRP since the beginning, yes.
By the way, you gave an in-person talk to Great South Bay Radio Club (Long
Island, NY) a few years ago. We really enjoyed it and would love to do a
repeat, plus another one for Suffolk County Radio Club. Are you interested?
Zoom is fine if you're not local.
I believe you're thinking of someone else. I've never been to (that part of) New York.
Please, capture the information I asked for from the VX-177 so I can have a look, thanks.
Updated by Pres Waterman 8 months ago
- File config.txt config.txt added
- File Yaesu_VX-170_20241021.img Yaesu_VX-170_20241021.img added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241014]
This is a VX-177 (UHF) as read under the model type VX-170 (VHF)
Updated by Pres Waterman 8 months ago
Dan,
Issue 11624 https://www.chirpmyradio.com/issues/11624#change-42953 has
been updated. Please note, the file name is VX-170 (VHF) but the actual
radio is VX-177 (UHF)
73
-Pres W2PW
Updated by Dan Smith 8 months ago
Here is a module you can try, using LoadingTestModules. Please test and report. Note that images you captured of your VX-177 as a VX-170 will need to be re-downloaded now that CHIRP knows the difference.
Before we can fully fix this, I need to know what tone mode is in your memory number 10. CHIRP shows it as red with an exclamation mark because it doesn't recognize it. Can you please tell me what the radio thinks the tone mode is?
Updated by Pres Waterman 8 months ago
- File config.txt config.txt added
- File Yaesu_VX-170_20241021.img Yaesu_VX-170_20241021.img added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241014]
VX-177 after download, then upload. Developer mode off, CHIRP restarted
Updated by Pres Waterman 8 months ago
Hi
Memory 10 in actuality is
RX 443.9
TX 448.9
DCS 631 enc/dec
Memory 10 itself is intact after download/upload.
I didn't know Developer Mode was on.
I was mis-remembering. Uploading (after downloading) works as expected.
However, trying to enter a valid 440 frequency on line 24 results in:
[image: image.png]
Are you available to look at this via Zoom? It could go a lot quicker being
truly interactive.
-Pres
On Mon, Oct 21, 2024 at 6:09 PM Dan Smith redmine@chirpmyradio.com wrote:
Updated by Dan Smith 8 months ago
Memory 10 in actuality is
RX 443.9
TX 448.9
DCS 631 enc/dec
This doesn't match what the driver thinks. What happens if you program a new memory with CHIRP as DCS and upload it to the radio? What tone mode does the radio think that is?
However, trying to enter a valid 440 frequency on line 24 results in:
Your image shows that you're still downloading it as a VX-170, so it's enforcing the VHF rules. Again, please read and follow LoadingTestModules, load the module from this issue, then try downloading the VX-177 by choosing it in the model box (do not choose VX-170). Then it should enforce the proper frequency range.
Updated by Pres Waterman 8 months ago
OH! I didn't know you have a test module for that radio. I'll try that.
-73
On Tue, Oct 22, 2024 at 7:46 PM Dan Smith redmine@chirpmyradio.com wrote:
Updated by Pres Waterman 8 months ago
- File config.txt config.txt added
- File Yaesu_VX-177_20241022-1.img Yaesu_VX-177_20241022-1.img added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241014]
OK we're getting close. I installed the module, downloaded and uploaded. It's no longer fighting me for the frequency since you updated it. Things are generally good with one exception I've noticed. DTCS does not work. I have (only) 2 channels: 7 and 9 which are programmed to DCS 631 but the radio is not using DCS. The 'T' and 'SQ' icons are flashing. It is not encoding tone, and does not require tone to open.
Updated by Dan Smith 8 months ago
Yeah, which is why I asked you above to confirm what happens on the radio when chirp sets a channel as DCS. However, I've been looking at a driver that is similar to this one and I think I figured out the issue. Please try this new one using the same procedure and see if it handles DCS properly. This was apparently always broken in the VX-170 driver.
Also, this one should error if you try to download a 170 as 177, and vice versa. Because of Yaesu's (brain dead) protocol, it can only do this after the image has been downloaded and checked. If you could please confirm this new check/failure behavior works, I'd appreciate it.
Updated by Pres Waterman 8 months ago
- File config.txt config.txt added
- File Yaesu_VX-177_20241022-2.img Yaesu_VX-177_20241022-2.img added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20241014]
SUCCESS! Thank you!
Updated by Dan Smith 8 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|e57bb3d678a55618862e83f25ef53b11fd567ad8.