New Model #2531
openYaesu FT-991
Added by roberto figuccio over 9 years ago. Updated 4 months ago.
0%
Description
new model from yaesu whith upgrade of 20 mar
Files
| FT-991-Exchange.xlsx (301 KB) FT-991-Exchange.xlsx | FT-991 Packet Capture Exchange | Stephen Ireland, 03/15/2016 05:47 AM | |
| ft-991a-memory-map.txt (24 KB) ft-991a-memory-map.txt | Dave Wiegman, 02/01/2024 04:02 AM |
Updated by Reink van Dijk over 9 years ago
The Yaesu FT-991 doesn't store all information with the stored memory.
- Names aren't stored with the memory
- CTCSS/DCS aren't stored with the memory (the FT-991 has a global setting for this)
Probaly using the CAT commands for programming the FT-991's memory (and settings) seem a good solution for me, the CAT commands are documented online but there seems to be a little difference in the documented commands and the commands with the latest firmware of the FT-991.
Updated by Håken Hveem about 9 years ago
Still waiting for a solution on this, it is 6 months since anything happened here.
Updated by Johan Adler almost 9 years ago
I just ordered one of these (will sell my Kenwood TS-2000). Anything I can do to help when I get it?
Is there any other model with similar CAT commands and memory structure that I might use as a starting point?
Updated by Stephen Ireland over 8 years ago
I have a need for cheap cross-radio-cross-model software and have been approaching Yaesu for information. Performing "Serial Port Monitor" traces and dumps does not provide considerably useful information either.
Usefull communication trail provided at the base of this posting. This communication trail could be used as a learning point for obtaining needed information from Yaesu (i.e. japanese engineers can be extremely literal).
I would suggest that the "status" of this project should be upgraded as the numbers of these radios out there are now considerable.
...............
Dear Steve,
Thank you for your patronage to the YAESU product.
Unfortunately, you cannot write the memory tag using CATS API.
In order to operate the radio as you mentioned, you will need a programming software. Please visit the RT Systems’ website and purchase one for FT-991.
http://www.rtsystemsinc.com/SearchResults.asp?Search=FT-991
We hope this information is useful and thank you for your continued support to YAESU. We remain,
Very truly yours,
Customer Relations Department
Yaesu Musen Co., Ltd.
From: Steve [mailto:vk3sir@hotmail.com]
Sent: Tuesday, March 8, 2016 9:38 AM
To: YAESU Customer Relations
Subject: CAT Programming - Memory tags FT-991
Hi,
I have been referred to this address via Tim Factor, one of your agents (email attached). Please note that this is not a service related issue but is an issue of general support – how to actually do something that is not documented.
I see from the CAT reference for the FT-991 that it is easy to use CAT codes to upload data to memories, yet I note that the FT-Systems Software also writes the "Memory Tags" as well.
How do you write the memory tag (i.e. to label a memory with say a repeater name) to the radio using the CAT programming API?
Once you have loaded memories, along with label tags, how do you read this data back?
Can you please forward me information on how to do this on the FT-991, and perhaps make this available to the wider community via the CAT Technical Supplement?
Thanks
Stephen I
VK3VM / VK3SIR
Updated by Stephen Ireland over 8 years ago
- File FT-991-Exchange.xlsx FT-991-Exchange.xlsx added
More information on the Process used to write to memory:
Shown below is the "handshake" with the RT Systems software on a "Write":
Codes Dir Tag Note
49 44 3b W ID
49 44 30 35 37 30 3b R ID 0570
53 50 49 44 3b W SP ID
53 50 49 44 47 30 58 50 41 3b R SP ID Serial
53 50 52 0 7 fc 3b W SP R
53 50 52 0 7 76 a5 17 3b R SP R ???
4d 43 3b W MC
4d 43 30 30 31 3b R MC 001
56 4d 3b W VM
4d 43 3b W MC
4d 43 30 30 31 3b R MC 001
45 58 30 38 30 30 31 30 30 3b W EX 0800100
45 58 30 38 31 31 30 30 30 3b W EX 0811000
45 58 30 38 32 30 36 30 30 3b W EX 0820600
45 58 30 38 33 30 35 30 30 30 3b W EX 08305000
53 50 52 2f e8 0c 3b W SP R
53 50 52 2f e8 0 ff 0b 3b R SP R
53 50 57 2f e8 1 ff 11 3b W SP W
41 3b R ACK
4d 43 3b W MC
4d 43 30 30 32 3b R MC 002
53 50 57 2f e9 1 0 13 3b W SP W
41 3b R ACK
53 50 57 2f eb 0 0 14 3b W SP W
41 3b R ACK
53 50 57 2f ed 0 0 16 3b W SP W
41 3b R ACK
53 50 57 2f ef 0 0 18 3b W SP W
41 3b R ACK
....
Shown below is the "handshake" with the RT Systems software on a "Read":
Codes Dir Tag Note
49 44 3b W ID
49 44 30 35 37 30 3b R ID 0570
53 50 49 44 3b W SP ID
53 50 49 44 47 30 58 50 41 3b R SP ID
45 58 30 38 30 3b W EX 080
45 58 30 38 30 30 31 30 30 3b R EX 0800100
45 58 30 38 31 3b W EX 081
45 58 30 38 31 31 30 30 30 3b R EX0811000
45 58 30 38 32 3b W EX 082
45 58 30 38 32 30 36 30 30 3b R EX 0820600
45 58 30 38 33 3b W EX 083
45 58 30 38 33 30 35 30 30 30 3b R EX 08305000
53 50 52 2f e8 0c 3b W SP R
53 50 52 2f e8 60 ff 6b 3b R SP R
53 50 52 2f e9 0d 3b W SP R
53 50 52 2f e9 ff ff 0b 3b R SP R
53 50 52 2f eb 0f 3b W SP R
53 50 52 2f eb ff ff 0d 3b R SP R
53 50 52 2f ed 11 3b W SP R
53 50 52 2f ed ff ff 0f 3b R SP R
53 50 52 2f ef 13 3b W SP R
53 50 52 2f ef ff ff 11 3b R SP R
53 50 52 2f f1 15 3b W SP R
53 50 52 2f f1 ff ff 13 3b R SP R
Conclusions:
(a) CAT Code 53 50 has two main variants:
- SPR (53 50 52)
- SPW (53 50 57)
(b) After Execute of SP R or SP W appears to be the memory address, in HIGH, LOW-order byte format
(c) Next 3 bytes appear to be payload data - though it seems to increment in 32-bit increments. So what each octet does needs further investigation. - Which are data? What is the 3rd element? is it a Checksum?
(d) After a SP W there is an ACK (CAT Code 41) written back
(e) The SP R and SP w Commands Definitely appear to read/write a 32-bit number into the FT-991's memory. The data retrived above the set of "SP" sequences appears to retrieve addresses used to locate the start of the data table.
(e) I am not sure with the read back.... Assistance needed.
.....
A sample Excel sheet with data is attached.
Regards,
Steve I
Updated by Bernhard Hailer almost 5 years ago
- Subject changed from yaesu ft991 to Yaesu FT-991
- Assignee deleted (
Ben Weiss) - Target version set to chirp-legacy
Updated by Gregg Horton over 3 years ago
Is there any progress on this on anything needed to make this happen?
Updated by Pavel Milanes over 3 years ago
Gregg Horton wrote:
Is there any progress on this on anything needed to make this happen?
Hi Gregg & all, two things are needed to develop a drivers for a radio (any radio) in Chirp:
A willing Developer (remember this is done pro-bono in dev's free time)¶
A radio in the hands of that developer (Own, loan, crowdfunding, gift, etc.)¶
For example, I had one radio driver started in 2019 with a short loan, but I had to return it before driver completion; now in 2021 I got a gift of one of those radios again, support was completed in about 3 days (it was a super simple old radio, driver still on production queue to be reviewed & approved)
So a loan offer will increase the odds by tempting a developer with some free time to start development.
I'm a willing developer, but my county custom laws are a obstacle to ship any radio here, I have to use non official channels and that way is expensive and can take a while... (I live in Cuba island)
Cheers, Pavel.
Updated by Dave Emrich over 2 years ago
Hi everyone,
I own a FT-991A with current firmware (as of 2022), and I am willing to learn what it takes to become a developer to help get CHIRP working on this radio. HOWEVER, I must advise that I am full-time employed so I will not have a lot of time in any given week. If this is acceptable to this community, please advise provide me a pointer to a "how to get started developing CHIRP drivers" page :-)
Cheers, Dave VK6KV
Updated by Jim Unroe over 2 years ago
Hi Dave,
On the "CHIRP home page":https://chirp.danplanet.com/projects/chirp/wiki/Home there is a "Documentation":https://chirp.danplanet.com/projects/chirp/wiki/Documentation link. It is at the end of step @#2@ of the To Get Started: section. For some reason this hypertext link doesn't stand out as being a link when I look at in on my monitor. Click this link to go to the "Documentation":https://chirp.danplanet.com/projects/chirp/wiki/Documentation page.
At the bottom of the Documentation page there is a "Developers":https://chirp.danplanet.com/projects/chirp/wiki/Developers link that will take you to the "CHIRP Developers":https://chirp.danplanet.com/projects/chirp/wiki/Developers page. This is what I referenced quite a bit when I got started.
Jim KC9HI
Updated by Bernhard Hailer almost 2 years ago
- Has duplicate New Model #9383: Yaesu FT991 added
Updated by Dave Wiegman 10 months ago
- File ft-991a-memory-map.txt ft-991a-memory-map.txt added
I was able to map the memory for the 991A, but have run out of time to work on it right now. Gil Kloepfer KI5BPK, https://www.kloepfer.org/ft991a/, did a lot of work on mapping the memory of the 991A, I did find a few things he missed. Unfortunately I do not have time at the moment to continue working on it. I figured I'd provide the memory map so that someone else that understands adding radios to Chirp better than I do and has more time at the moment can run with it.
Dave K4DRW
Updated by Darek SP4UBW 4 months ago
In the meantime, several programs for programming memory channels and settings have been developed. Chirp still lacks this feature. Once I finish linking all the functions in FT991(A), I might work on a plugin for Chirp.
I can't promise 100% because my program already allows reading and writing settings and channels, but I'll try to add something here as well. :)