New Model #5329

Yaesu FT-70DR

Added by Nicolas Pike almost 3 years ago. Updated 7 months ago.

Status:Closed Start date:11/07/2017
Priority:Normal Due date:
Assignee:Nicolas Pike % Done:

100%

Category:-
Target version:chirp-daily
Chirp Version:daily Equipment Loan Offered:No

Description

FT-70-CHIRP-ProgrammingInstructions.pdf - FT-70DR Programming With CHIRP - Tips & Tricks (65.6 kB) Bruce Layne, 01/02/2020 03:36 am

Associated revisions

Revision 2957:bc008caf0471
Added by nicolas jon pike over 2 years ago

New Model #5329
FT70 Driver I now have enough of the driver working to be useful.
Read / write memories, a number of the settings, and import from RepeaterBook work.
Saving modes dn,vw and AMS in memory channels, do not currently work.
Banks have not been tested - may now work, VFO settings not implemented (etc)

I have also raised a request for C4FM to be added to CHIRP Modes.

Revision 2961:056ccab1b395
Added by Nicolas Pike over 2 years ago

[FT-70] Banks support fixes for New Model #5329
Some pep8 fixes to Sorry.

Revision 2964:61ba9c815170
Added by Nicolas Pike over 2 years ago

[FT-70] New Model #5329 Always Save/Display as memory name (For the moment..)

Revision 2966:9e3b0ff76308
Added by Nicolas Pike over 2 years ago

[FT-70] #5329 and issue #5647 Revise handling of empty chunks in yaesu_clone.py
#5647 Empty chunks no longer counted towards blocks read.
#5329 Can now set correct memory size read request, as no getting empty blocks.
Yaesu_clone change proposed by Dan - Thanks! I have only tested it on the FT-70, would be great to see it tested on other Yaesu radios.
This replaces my last submitted patch.

Revision 2973:012125aa069c
Added by Nicolas Pike over 2 years ago

[FT-70] #5329 Corrects handling of Mycall string – Thanks Fred.

History

Updated by Nicolas Pike almost 3 years ago

I have made a start based on the FT1.

Can read radio
Display memories
Display some radio settings

*Help/guidance appreciated, particularly on - *

Checksums - location/ storage?
Single VFO - memory map layout?
How to handle Fusion Groupids, pager etc? FT1 driver does not appear to handle these. Whatcha really needed?
Another other radios that it shares features with?

Updated by Nicolas Pike almost 3 years ago

Progress

Learnt a lot about CHIRP..

The basics for reading and writing memories (minus modes) now work!

Read FT70 and checked checksum
Imported entries from RepeaterBook
Write FT70 with checksum successfully!

TODO / Understand

Single VFO - memory map layout?
Communications Mode ? AMS,FM DN,DW TX vs RX?
Mode not currently stored in memories - ALL show as FM but memories
SKIP test/where stored
Check storage of steps
Pager and group mode/ids ?
Triple check/ understand _memsize and _block_lengths
Bank name lanbel name size display 6 store 16? same for Mycall and message
Update Menu system just for the features we have understood!
CHIRP mode DIG not supported. - is there a CHIRP Fusion mode? Auto?
Doubtless lots else...

Updated by Nicolas Pike almost 3 years ago

Updated radio firmware to 1.11 which supports Wires-X

All memories now display frequency instead of name. Display tag bit will need to be set
Skip works, mask works (but not settable in display)
Need to clarify FF padding for labels/size
Not clear how mode is stored particularly if AMS is on?
CHIRP mode DIG not supported. - is there a CHIRP Fusion mode? Auto? or just DIGI
Priority, SQLl, Bell, Attenuation stored "Somewhere"?
Auto Step?
No progress on Pager/group modes

Added to memory map

Display tag
Clock shift (!)
AMS selected
Deviation

Updated by Ariel H over 2 years ago

Has there been any progress on this? If not can I get whatever code you have written and take over the work?

Updated by Nicolas Pike over 2 years ago

Sorry about the lack of progress. Christmas and life.
Anyway I am back on the trail. I have emailed Ariel H
Anyone else interested in testing?

Updated by Matthew "Juniper" Barlett over 2 years ago

Nicolas Pike wrote:

Sorry about the lack of progress. Christmas and life.
Anyway I am back on the trail. I have emailed Ariel H
Anyone else interested in testing?

I have made a start based on the FT1.

Mr. Pike,

BLUF: I want to help, not sure how.

Radio Make: Yaesu
Radio Model: FT-70DR
CHIRP Version: CHIRP daily-20170714
OS: Ubuntu 16.10

I am unable to locate the FT1 radio model you reference. (Unless FT-1D).

I have tried `Radio` > `Download From Radio` all of the models under Yaesu with no success.

Observations:

(This is mainly for others viewing this issue)

It would appear that the default method of cloning the FT-70DR is Radio-to-Radio using the Mic/Sp jack:
  • Disconnect battery, turn device off
  • Connect Radio-to-Radio via the Mic/Sp jack (cable not supplied)
  • Plug in Radio to AC power using supplied transformer
  • Hold down the `F` key while holding down the `Power` key
  • The display says "CLONE"
  • Press the `BAND` key to send
  • The display changes to "--TX--"
  • (since I only have 1 device I don't know what happens next)
The only way I can see to have the Radio link via USB/Serial is:
  • Connect Radio as above, except connect the supplied USB cable to a computer and the radio using the DATA jack
  • Hold down the `AMS` key while holding down the `Power` key
  • The Radio display says "ADMS"
  • The Radio shows up as `/dev/ttyACM0` on my computer
If I don't initialize the clone from the Radio the following happens:
  • Run `Radio` > `Download From Radio` from CHERP
  • A "Cloning" dialog box opens
  • After a few seconds a "No response from radio" error occurs
If I initialize the clone from the Radio the following happens:
  • Run `Radio` > `Download From Radio` from CHERP
  • A "Cloning" dialog box opens
  • Press the `BAND` key on the Radio
  • The Radio display changes to "--TX--" (like in the clone over Mic/Sp listed above)
  • After a few seconds the clone times out on the Radio & CHIRP at the same time
  • The Radio display says "ERROR"
  • CHERP errors with "No response from radio"

Updated by Nicolas Pike over 2 years ago

Ariel H has joined the project! Other testers and developers are very welcome, we should have a testable CHIRP driver very soon. Thanks!

*FT-70D Programming using the supplied USB cable *

Forget all the power on, mains unplug confusions of the Youtube videos.
To get programming (ADMS) mode using USB all you "actually" have to do is this.

1. Ensure the radio is switched on.
2. Unclip the battery - Just so it is not connected.
3. Hold in the power on and AMS buttons, while clipping the battery back on.
4. ADMS is displayed - The radio is now in USB programming mode.

This procedure does require some dexterity - as you will find. But works, and is way simpler than the mains unplugging/plugging performance.

*Other combinations will show ADMS but - do not - work*

Updated by Terrence Koeman over 2 years ago

Just so you know, I used the jack to USB cable I normally use for my FT-60, and CHiRP will successfully load using clone mode from the radio when I use "VX-8DR" as radio. The data seems OK too.

When I use the FT-1D the progress bar will be at half for CHiRP when it is full on the radio, so it seems the "VX-8DR" is a better match. I will now update some settings and attempt to write to the radio and will report back.

Updated by Terrence Koeman over 2 years ago

Hmm, the upload seems to go without errors (just like the download), however I did notice that the data is probably not completely right. The channel data is corrupted when downloading with the VX-8DR driver, and there's garbage in the memory bank names.

I would guess someone would need to sort out the locations of the various data in the image.

Updated by Nicolas Pike over 2 years ago

Alpha, work in progress FT70 patch submitted for review. Comments appreciated. Thanks.

Updated by Bill Broadley over 2 years ago

Is it available to try somewhere? A pull request maybe?

Just got a FT-70dr, not sure what to try. Seems like the two modes are clone mode, and USB programming mode. Sounds like the using the VX-8DR profile almost works, but somewhat corrupts the uploads.

Writing support from scratch is a bit daunting, but I could potentially help with something that's relatively close.

Updated by Nicolas Pike over 2 years ago

Bank name now saves correctly
Temp changed back to 2 modes

nicolass-Mac-mini:tests nicolas$ python run_tests.py d Yaesu_FT-70D
Yaesu FT-70D Detect PASSED: All tests
Yaesu FT-70D Settings PASSED: All tests
Yaesu FT-70D Clone PASSED: All tests
Yaesu FT-70D Edges PASSED: All tests
Yaesu FT-70D BruteForce PASSED: All tests
Yaesu FT-70D CopyAll PASSED: All tests
Yaesu FT-70D Banks PASSED: All tests
---------------------------------------------------------------------

Results:
TOTAL : 7
FAILED : 0
SKIPPED: 0
PASSED : 7
CRASHED: 0

Updated by Nicolas Pike over 2 years ago

Bank name now saves correctly
Temp changed back to 2 modes 

nicolass-Mac-mini:tests nicolas$ python run_tests.py -d Yaesu_FT-70D
    Yaesu FT-70D        Detect      PASSED: All tests
    Yaesu FT-70D        Settings    PASSED: All tests
    Yaesu FT-70D        Clone       PASSED: All tests
    Yaesu FT-70D        Edges       PASSED: All tests
    Yaesu FT-70D        BruteForce  PASSED: All tests
    Yaesu FT-70D        CopyAll     PASSED: All tests
    Yaesu FT-70D        Banks       PASSED: All tests
----------------------------------------------------------------------
Results:
  TOTAL  : 7
  FAILED : 0
  SKIPPED: 0
  PASSED : 7
  CRASHED: 0

Updated by Nicolas Pike over 2 years ago

I now have enough of the driver working to be useful.
Read / write memories, a number of the settings, and import from RepeaterBook work.
Saving modes dn,vw and AMS in memory channels, do not currently work.
Banks have not been tested - may now work, VFO settings not implemented (etc)

I have also raised a request for C4FM to be added to CHIRP Modes.

Updated by Nicolas Pike over 2 years ago

  • Assignee set to Nicolas Pike
  • % Done changed from 0 to 70

First version now in daily builds.

Please Note

Read / write memories, a number of the settings, banks, and import from RepeaterBook work.

Bank Name length not checked on gui input - but first 6 characters are saved correctly. Extended characters entered as bank names on radio are shown incorrectly in Chirp display.
Mode FM/AM/AMS not currently stored in memories - ALL show as FM in memories.

Feedback appreciated.

Nicolas

Updated by M T over 1 year ago

Hi Nicolas! Thanks for all of this painstaking work. I've been testing it out recently. One thing I noticed: a 6.25 kHz step is prohibited, but the radio is capable of it. (There are probably other valid step values that aren't available, including "auto".) Just thought I'd make note of it here.

Please let me know if there's anything I can do to assist.

Updated by Nicolas Pike over 1 year ago

  • Chirp Version changed from 0.4.0 to daily

Thanks for your feedback. Sorry I have not progressed this for awhile. code and suggestions always appreciated.
Nicolas

Updated by Brad Allen 11 months ago

Which cable do I use for the most working version?

I already own the USB to Data cable, but I would like to know if I should purchase the Audio-USB cable instead for this to work.

Updated by Bruce Layne 9 months ago

Brad Allen - Use the USB cable supplied by Yaesu with the FT-70DR. I inadvertently tried a USB charging cable (no data lines) and that obviously dodn't work, but I also tried a USB cable that I know was wired for data and that didn't work either but the Yaesu cable did work.

Updated by Bruce Layne 9 months ago

After some struggling to program the FT-70DR with CHIRP in Linux and believing I had partially bricked the radio (USB communications stopped working), I eventually was able to figure it out and can now program the FT-70DR most of the time without problems. I created a PDF with some suggestions based on what I learned the hard way, partly so I can program the radio in a few months when this pain is forgotten, but also to hopefully help others who may be struggling to program an FT-70DR. I attached the PDF file.

It would be great to have some CHIRP support for Yaesu System Fusion, but here's a suggestion that might be easy to implement. Convert the Name field to all upper case characters. Entering lower case characters resulted in spaces when uploaded to the FT-70DR, presumably because those characters couldn't be displayed.

Updated by Bernhard Hailer 7 months ago

  • Status changed from New to Closed
  • Target version set to chirp-daily
  • % Done changed from 70 to 100

Appears to be complete.
If there are further issues with this driver, please open a new bug report. Thanks!

Also available in: Atom PDF

prevent spam