CHIRP

I also have this HT... !was hoping Chirp would have it on it's list by now. Waiting patiently!

I am in possession of ADMS-14 source code. I can share it with anyone interested.

Hoping for a CHIRP update that allow this Yaesu flagship HT to be programmed, so far there's no method to program 11/2022

I recently purchased two of these radios, and after putting some frequencies in the memory, I told it to back-up the memory to SD card and had a look.

Here's a subset:

00002aa0 02 10 14 68 75 c1 00 00 34 44 42 20 52 65 64 6c |...hu...4DB Redl|
00002ab0 61 6e 64 73 20 32 6d ff 00 06 00 09 00 0d 00 18 |ands 2m.........|
00002ac0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000030e0 03 17 43 82 00 c1 00 00 34 5a 42 20 42 72 69 73 |..C.....4ZB Bris|
000030f0 62 61 6e 65 20 37 30 63 00 50 00 09 00 0d 00 18 |bane 70c.P......|
00003100 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|

Those are the entries for VK4RDB Bayside 146.875MHz and VK4RZB Mt. Coot-tha 438.200MHz; both FM repeaters with a 91.5Hz CTCSS.

Simplex looks similar, for instance, the national 2m APRS frequency 145.175MHz (channel 999):
000094c0 02 00 14 51 75 d0 00 00 41 50 52 53 20 32 6d ff |...Qu...APRS 2m.|
000094d0 ff ff ff ff ff ff ff ff 00 06 00 0c 00 0d 80 18 |................|
000094e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|

I don't know how this compares to prior models, but what I do know just looking at that hex dump:

• each memory channel is 32 bytes long
• first byte is a band indicator? (0x02 for 2m, 0x03 for 70cm?)
• the frequency is stored in BCD; byte offset 2-4
• ASCII memory tag is in byte offset 8-15; not sure if byte 16 is a null terminator or if that 0x00 means something else
• the general memory channels start at offset 0x17e0 (channel 150 is at 0x2aa0; 200 at 0x30e0… etc)

Some more reverse-engineering notes… the first section of the file seems to be a "flags" register that indicates what channels are used.

I added two simplex frequencies in slots 1 and 2. 1 was already preset with a factory default, but 2 was previously clear. Note the byte at 0x000012c1 changed from 0x00 to 0x03.

00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|

• * 000012c0 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| | 000012c0 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000012d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000012d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

Here are the actual channels I added/changed:

00001800 02 00 14 50 00 d0 00 00 ff ff ff ff ff ff ff ff |...P............| | 00001800 02 04 14 65 00 c0 00 00 32 6d 20 63 61 6c 6c 69 |...e....2m calli|
00001810 ff ff ff ff ff ff ff ff 00 06 00 0c 00 0d 80 18 |................| | 00001810 6e 67 ff ff ff ff ff ff 00 06 00 09 00 0d 00 08 |ng..............|
00001820 02 00 14 55 20 00 00 00 ff ff ff ff ff ff ff ff |...U ...........| | 00001820 03 04 43 90 00 c0 00 00 37 30 63 6d 20 63 61 6c |..C.....70cm cal|
00001830 ff ff ff ff ff ff ff ff 00 06 00 08 00 0d 00 08 |................| | 00001830 6c 69 6e 67 ff ff ff ff 00 50 00 09 00 0d 00 08 |ling.....P......|

So ch1 I changed the simplex frequency from 145000kHz (default) to 146550kHz (Australia national 2m calling frequency).
Ch2 apparently was set to 145520kHz, but due to the flag in the earlier block, was seen as "unused".

Did some more reverse-engineering work… I came up with this:

https://github.com/sjlongland/chirp/commit/fffd6eecfefcc673c8b6e8ae3d7b5d120d55637a

It appears it's a very different layout to the FT3D. The vacancy flags appear to be the same as the FT1D/FT2D/FT3D, but it is at a different memory location. The actual channel seems to have quite different fields. Note the assert statements at the bottom: I don't know what those values mean yet.

Can anyone get me a file saved from the FT5 ADMS software? It seems like it won't let me save out an empty file, maybe without a radio?

I've decoded the ft1, 2, and 3 ADMS formats now, which is handy, so looking at the FT5 file from that software should help determine some differences.

Dan Smith wrote in #note-9:

Can anyone get me a file saved from the FT5 ADMS software? It seems like it won't let me save out an empty file, maybe without a radio?

I've decoded the ft1, 2, and 3 ADMS formats now, which is handy, so looking at the FT5 file from that software should help determine some differences.

I've got one on the way from Gigaparts, should be here mid week. Anything you need, I'll be happy to do whatever I can to provide it to help get this radio spun up in CHIRP. Welcome to email me at W5JDC@outlook.com but I'll keep an eye out here as well.

After playing with the ADMS-14 software some more today I've learned it's a little strange about opening files. Users cannot go back and open a .ft5d file immediately. One first needs to either clone the current state of the radio into the software from Communications(C)->Get Data From FT5D(G) or import a BACKUP.dat file from Communications(C)->Get Data From SD Card(D) menu. After doing so users can open almost any previous .ft5d save file available. I learned that the current software v1.0.1.0 cannot open a .ft5d created by a previous version of the software. So to open the .ft5d file I provided earlier one should take the previously attached BACKUP.dat file, import it with Communications(C)->Get Data From SD Card(D) and then that data could be saved as an .ft5d file or the one I provided can be opened. After opening the file I provided if you need to create a BACKUP.dat file from it Communications(C)->Send Data to SD Card(U). It can be stored anywhere but the software will only open it if it's named BACKUP.dat.

I have a FT5D I'm willing to offer as a loaner. Not sure how that process works, but I'd love to see it implemented. Please reach out on this thread (for visibility) if this is something you'd like to pursue!

No news on this? :-(