New Model #7387
Yaesu FT-4VR
| Status: | Closed | Start date: | 12/01/2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Bernhard Hailer | % Done: | 100% |
|
| Category: | - | |||
| Target version: | chirp-daily | |||
| Chirp Version: | daily | Equipment Loan Offered: | Yes |
Description
Have radio and USB
Associated revisions
[ft4] driver restructure (#7615)
While implementing two more radios of the Yaesu FT-4 family (the FT-25, see #7543, and the FT-4V, see #7387), I found that with some moderate reorganization, implementation of new radios will become easier. The proposed reorganization implements one more interstitial layer of inheritance to support the sub families of FT-4 (containing the FT-4X and FT-4V) and FT-65 (containing FT-65 and FT-25). Also, some variable assignments have been moved from the individual radio classes to the SCU-35 base class and to the interstitial classes named above.
This change also adds the infrastructure for adding European or Asian models, and as such prepare for addressing a number of currently open issues (6.25kHz tune step issues on EU models, frequency limitations; see #6619, #6651, #6677, #6761, #6869). It will also make it easier for a few additional fixes for issues which were found during my work on this driver (#7601, #7603, #7605). I will submit these fixes in additional patches.
Fixes: #7615
[ft4] Add Yaesu FT-4VR (and infrastructure for Yaesu FT-4VE). Fixes: #7387
This patch adds support for the Yaesu FT-4V to Chirp. The European version is commented out; we can activate as soon as we obtain an image (it can be downloaded using FT-25R as selected radio).
History
Updated by Bernhard Hailer over 1 year ago
- Status changed from New to Feedback
Did you try the FT-4 selection in Chirp? It needs to be a recent version of Chirp. If you did try, what happened, and can you provide a log?
Updated by Matt Atwood over 1 year ago
Thanks for the recommendation Bernhard. I did select FT-4XR in CHIRP - it is the only FT-4 selection available. Upon initiating transfer (Download from radio) I received an error message from CHIRP "Failed to communicate with radio: Incorrect ID read from radio". I assume I need to enter "CLONE" mode on the XCVR, which I did, in both TX and RX mode, as well as just turning the HT on and attempting to query the radio. I have tried several permutations of the process to get the radio to clone and it fails every time. I am using CHIRP version 20200107.
Where do I find the log that you asked about? I am unable to locate a log file of any kind for CHIRP.
Updated by Bernhard Hailer over 1 year ago
For how to retrieve the log, please refer to the Wiki: How To Report Issues. The log will definitely tell us more.
Updated by Matt Atwood over 1 year ago
- File debug(Clone Mode).log added
- File debug(TX Mode).log added
Thank Bernhard. Attached are the logs. The first (TX Mode) had the radio in CLONE / TX mode. The second, (CLONE Mode) had the radio in just CLONE mode.
Updated by Bernhard Hailer over 1 year ago
- Assignee set to Bernhard Hailer
Ah - it is a new model! This radio identifies as "IFT-15R", while the FT-4R is "IFT-35R".
I can add this radio, but I would be flying blind. Let me dive into the manual for the FT-4V. I hope I can say a little more soon...
Updated by Matt Atwood over 1 year ago
Thanks Bernhard! If a radio is needed, I have a unit to test with.
Updated by Bernhard Hailer over 1 year ago
- File ft4.py added
- Target version set to chirp-daily
- % Done changed from 0 to 90
Hi Matt, I did a "blind flight", and it might just work.
To help me test this, please download the attached ft4.py and launch chirp.
1. enable developer mode: help -> check enable developer functions
2. load this module: file -> load module, point to the ft4.py you downloaded
3. open radio communication as usual but select FT-4V as radio model from list
4. perform any testing, download/upload, modifications etc.
In case you have to restart chirp, you will have to repeat step 2 again to use this modified candidate.
Please let me know how it goes, and I'll submit a patch to chirp. To enable me to do that, I need to ask you for an image from your radio; when you prepare one for me, please ensure that there's no private information in it you don't want to share: an image right after a factory reset is fine. That image is needed for testing before I'm allowed to submit.
Updated by Matt Atwood over 1 year ago
It works perfectly! I was able to download from the radio, as well as upload to it. I will reset the radio tomorrow AM and send the img file to you. Thank you so much!
Updated by Bernhard Hailer over 1 year ago
Excellent, glad to hear! Please don't forget that image; without it I can't submit it.
Updated by Bernhard Hailer over 1 year ago
- % Done changed from 90 to 100
Updated by Bernhard Hailer over 1 year ago
- Status changed from Feedback to In Progress
Updated by Matt Atwood over 1 year ago
- File Yaesu_FT-4VR_Factory_Reset.img added
Here is the factory reset image. Thanks gain for your help!
- Matt
Updated by Bernhard Hailer over 1 year ago
Sorry, there's some delay; I need to restructure the base driver (ft4.py) first. That's essentially complete, but that patch needs to be accepted first. See #7615.
Updated by Anonymous over 1 year ago
- Status changed from In Progress to Closed
Applied in changeset 5a1de50496e1.
Updated by Bernhard Hailer over 1 year ago
WANTED:
Image of an FT-4VE. If you have one, please send it to me!
The image can be downloaded using "FT-4VR" as radio in Chirp. Once I have the image, I'll add the FT-4VE to Chirp.