CHIRP-next model report #10747
closedYaesu_VX-170 model test
Description
Hello, I noted a few models of radios I own whose CHIRP-next testing status is "Probably works" or "Implied", but the VX-170 driver doesn't appear to have been tested at all.
I hope that this test is useful to you as the model I use with this driver is the FT-270. I was advised several years ago when I first bought this radio to use it with the VX-170 driver, and this worked perfectly for me in the legacy versions of CHIRP. (If these are functionally the same, I wonder if it would be helpful to users to have it marked with both model numbers, or appear in the list as FT-270 as well, or some other way that makes sense to you... it would save FT-270 owners from having to ask, or worse, assuming their radio is unsupported.)
Anyhow, I have performed the suggested basic tests (download an image from the radio, edit a memory, upload back to radio, check the edit took place and other memories don't appear scrambled). If there is anything else you'd like tested on an FT-270, don't hesitate to reach out. 73!
Updated by Dan Smith about 1 year ago
Hmm, interesting. There has been a bunch of reports lately that the VX-170 does not work, which seems like maybe a firmware-related issue. I can alias the 270 to the 170 on the front page and reference this issue I guess. Do you know of any firmware changes and/or what firmware you've got for posterity and future fixes?
Updated by Jim Anderson about 1 year ago
Not sure how to check the firmware version - googling turned up nothing, the manual makes no mention of firmware at all, and I tried cycling through holding each button while switching it on but came up with nothing. (Holding Monitor while turning it on puts it in clone mode, and holding VFO while turning it on makes it emit a single high tone instead of an ascending tone sequence, but doesn't display anything other than the usual battery voltage meter while it powers on.)
It's an FT-270R and the serial number is 2G961584 - that's about all I've got unless you know how to get it to show the firmware version? Sorry.
Updated by Dan Smith about 1 year ago
I'm not a Yaesu fan, so I don't even know. The issues reported by people relate to the radio refusing the ID we send it on clone out and reporting a different ID on clone in. That's typically related to a firmware update that fundamentally changed the format of the memory and so the radio reports a different string so the software can identify the change.
Anyway, I'll add the 270 as working with the 170 driver on the front page, which I guess won't change anything related to that other problem (which only affects some users), but that's fine.
Thanks!
Updated by Dan Smith about 1 year ago
- Status changed from New to Closed
Applied in changeset github|51bb1e93ee51b85cda3c999db11a60e289d9f65d.