Project

General

Profile

Actions

New Model #7387

closed

Yaesu FT-4VR

Added by Matt Atwood almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
12/01/2019
Due date:
% Done:

100%

Estimated time:
Equipment Loan/Gift Offered:
Yes
I read the instructions above:

Description

Have radio and USB


Files

debug(Clone Mode).log (24.9 KB) debug(Clone Mode).log radio in just CLONE mode Matt Atwood, 01/25/2020 05:18 PM
debug(TX Mode).log (25.1 KB) debug(TX Mode).log radio in CLONE / TX mod Matt Atwood, 01/25/2020 05:18 PM
ft4.py (52.3 KB) ft4.py Yaesu FT-4X / FT-4V / FT-65 / FT-25 driver Bernhard Hailer, 01/26/2020 04:26 PM
Yaesu_FT-4VR_Factory_Reset.img (8.49 KB) Yaesu_FT-4VR_Factory_Reset.img Matt Atwood, 01/27/2020 01:16 AM
Actions #1

Updated by Bernhard Hailer almost 5 years 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?

Actions #2

Updated by Matt Atwood almost 5 years 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.

Actions #3

Updated by Bernhard Hailer almost 5 years 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 almost 5 years ago

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.

Actions #5

Updated by Bernhard Hailer almost 5 years 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...

Actions #6

Updated by Matt Atwood almost 5 years ago

Thanks Bernhard! If a radio is needed, I have a unit to test with.

Actions #7

Updated by Bernhard Hailer almost 5 years ago

  • File ft4.py ft4.py added
  • Target version set to chirp-legacy
  • % 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.

Actions #8

Updated by Matt Atwood almost 5 years 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!

Actions #9

Updated by Bernhard Hailer almost 5 years ago

Excellent, glad to hear! Please don't forget that image; without it I can't submit it.

Actions #10

Updated by Bernhard Hailer almost 5 years ago

  • % Done changed from 90 to 100
Actions #11

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from Feedback to In Progress
Actions #12

Updated by Matt Atwood almost 5 years ago

Here is the factory reset image. Thanks gain for your help!

  • Matt
Actions #13

Updated by Bernhard Hailer almost 5 years 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.

Actions #14

Updated by Anonymous almost 5 years ago

  • Status changed from In Progress to Closed

Applied in changeset commit:5a1de50496e1.

Actions #15

Updated by Bernhard Hailer almost 5 years 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.

Actions

Also available in: Atom PDF