[chirp_users] Yaesu FTM6000 support - not yet. Perhaps I can help?
I've used Chirp for my HTs now for many years (thanks, developers!), and recently bought a Yaesu FTM6000 dual-band mobile. Its primary deficiency from my point of view is that it isn't supported by Chirp, for which reason I bought a third-party programming program and serial cable made by RT Systems.
I'm not a fan of their business model of "Spend another $60 for a different (but actually near-identical) programming utility for every one of your different radios," so I view this as a one-time thing, and a way to give back by achieving Chirp support for this model.
I would be delighted to use this equipment and my embedded hardware/software development skills to bring about Chirp support for this radio, but I would need some help from someone familiar with Chirp internals. In particular, my Python skills are rudimentary; I can write Python, but it's not my best language. Implementing this support on my own seems rather daunting.
Here's what I can do well:
- Run test cases for reading/writing configurations from and to the radio with the third-party software - Intercept the serial data streams at either the USB driver level or the RS-232 serial link level (it's my understanding that this radio does indeed use RS-232 levels and async serial communications). Wireshark and logic analyzers are my friends! - Analyze the serial data streams for this radio and compare them to samples of known Yaesu programming protocols for other models (I believe they tend to re-use the same protocol for many models) - Compile and run test builds of a modified Chirp build from a Git repo and test them
Here's what I would need help with:
- Someone familiar with Python, the Chirp drivers, and ideally Yaesu's programming protocols, to work on the Python code to adapt an existing Chirp driver for the FTM6000.
Is there someone on the list who would be interested in working with me on adding support for this radio to Chirp?
Regards, Steve Hersey
I'm going to post this request on the developer's list instead, as that's probably the better place for it...
Steve
On Tue, May 16, 2023 at 12:46 PM Stephen Hersey n1xnxham@gmail.com wrote:
I've used Chirp for my HTs now for many years (thanks, developers!), and recently bought a Yaesu FTM6000 dual-band mobile. Its primary deficiency from my point of view is that it isn't supported by Chirp, for which reason I bought a third-party programming program and serial cable made by RT Systems.
I'm not a fan of their business model of "Spend another $60 for a different (but actually near-identical) programming utility for every one of your different radios," so I view this as a one-time thing, and a way to give back by achieving Chirp support for this model.
I would be delighted to use this equipment and my embedded hardware/software development skills to bring about Chirp support for this radio, but I would need some help from someone familiar with Chirp internals. In particular, my Python skills are rudimentary; I can write Python, but it's not my best language. Implementing this support on my own seems rather daunting.
Here's what I can do well:
- Run test cases for reading/writing configurations from and to the
radio with the third-party software
- Intercept the serial data streams at either the USB driver level or
the RS-232 serial link level (it's my understanding that this radio does indeed use RS-232 levels and async serial communications). Wireshark and logic analyzers are my friends!
- Analyze the serial data streams for this radio and compare them to
samples of known Yaesu programming protocols for other models (I believe they tend to re-use the same protocol for many models)
- Compile and run test builds of a modified Chirp build from a Git
repo and test them
Here's what I would need help with:
- Someone familiar with Python, the Chirp drivers, and ideally Yaesu's
programming protocols, to work on the Python code to adapt an existing Chirp driver for the FTM6000.
Is there someone on the list who would be interested in working with me on adding support for this radio to Chirp?
Regards, Steve Hersey
-- Steve Hersey N1XNX n1xnxham@gmail.com
"Any sufficiently advanced technology is indistinguishable from magic." -- Clarke's Third Law "Any technology distinguishable from magic is insufficiently advanced." -- Benford's Corollary "Any sufficiently advanced magic is indistinguishable from technology." -- Charles Stross, *Dead Lies Dreaming* “It's still magic even if you know how it's done.” -- Terry Pratchett
I also have the FTM6000 with the RT programming software and cable and can assist in testing. I am not an experienced programmer, but would love to assist as best I can.
The deficiencies with radios where the mfgrs do not provide enough info to allow free development of programming software is an issue.
I also have an FTM 100 that cannot be handled by chirp so that is an issue as well.
Jeff KI7GJG
On Tue, May 16, 2023 at 11:56 AM Stephen Hersey n1xnxham@gmail.com wrote:
I'm going to post this request on the developer's list instead, as that's probably the better place for it...
Steve
On Tue, May 16, 2023 at 12:46 PM Stephen Hersey n1xnxham@gmail.com wrote:
I've used Chirp for my HTs now for many years (thanks, developers!), and recently bought a Yaesu FTM6000 dual-band mobile. Its primary deficiency from my point of view is that it isn't supported by Chirp, for which reason I bought a third-party programming program and serial cable made by RT Systems.
I'm not a fan of their business model of "Spend another $60 for a different (but actually near-identical) programming utility for every one of your different radios," so I view this as a one-time thing, and a way to give back by achieving Chirp support for this model.
I would be delighted to use this equipment and my embedded hardware/software development skills to bring about Chirp support for this radio, but I would need some help from someone familiar with Chirp internals. In particular, my Python skills are rudimentary; I can write Python, but it's not my best language. Implementing this support on my own seems rather daunting.
Here's what I can do well:
- Run test cases for reading/writing configurations from and to the
radio with the third-party software
- Intercept the serial data streams at either the USB driver level or
the RS-232 serial link level (it's my understanding that this radio does indeed use RS-232 levels and async serial communications). Wireshark and logic analyzers are my friends!
- Analyze the serial data streams for this radio and compare them to
samples of known Yaesu programming protocols for other models (I believe they tend to re-use the same protocol for many models)
- Compile and run test builds of a modified Chirp build from a Git
repo and test them
Here's what I would need help with:
- Someone familiar with Python, the Chirp drivers, and ideally
Yaesu's programming protocols, to work on the Python code to adapt an existing Chirp driver for the FTM6000.
Is there someone on the list who would be interested in working with me on adding support for this radio to Chirp?
Regards, Steve Hersey
-- Steve Hersey N1XNX n1xnxham@gmail.com
"Any sufficiently advanced technology is indistinguishable from magic." -- Clarke's Third Law "Any technology distinguishable from magic is insufficiently advanced." -- Benford's Corollary "Any sufficiently advanced magic is indistinguishable from technology." -- Charles Stross, *Dead Lies Dreaming* “It's still magic even if you know how it's done.” -- Terry Pratchett
-- Steve Hersey N1XNX n1xnxham@gmail.com
"Any sufficiently advanced technology is indistinguishable from magic." -- Clarke's Third Law "Any technology distinguishable from magic is insufficiently advanced." -- Benford's Corollary "Any sufficiently advanced magic is indistinguishable from technology." -- Charles Stross, *Dead Lies Dreaming* “It's still magic even if you know how it's done.” -- Terry Pratchett _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to sandhillsinvestment@gmail.com at sandhillsinvestment@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Thanks, Jeff. I'll let you know once I have something I trust to inflict on anyone. May take a while.
Regards, Steve
On Tue, May 16, 2023 at 7:06 PM Jeffrey Vian sandhillsinvestment@gmail.com wrote:
I also have the FTM6000 with the RT programming software and cable and can assist in testing. I am not an experienced programmer, but would love to assist as best I can.
The deficiencies with radios where the mfgrs do not provide enough info to allow free development of programming software is an issue.
I also have an FTM 100 that cannot be handled by chirp so that is an issue as well.
Jeff KI7GJG
On Tue, May 16, 2023 at 11:56 AM Stephen Hersey n1xnxham@gmail.com wrote:
I'm going to post this request on the developer's list instead, as that's probably the better place for it...
Steve
On Tue, May 16, 2023 at 12:46 PM Stephen Hersey n1xnxham@gmail.com wrote:
I've used Chirp for my HTs now for many years (thanks, developers!), and recently bought a Yaesu FTM6000 dual-band mobile. Its primary deficiency from my point of view is that it isn't supported by Chirp, for which reason I bought a third-party programming program and serial cable made by RT Systems.
I'm not a fan of their business model of "Spend another $60 for a different (but actually near-identical) programming utility for every one of your different radios," so I view this as a one-time thing, and a way to give back by achieving Chirp support for this model.
I would be delighted to use this equipment and my embedded hardware/software development skills to bring about Chirp support for this radio, but I would need some help from someone familiar with Chirp internals. In particular, my Python skills are rudimentary; I can write Python, but it's not my best language. Implementing this support on my own seems rather daunting.
Here's what I can do well:
- Run test cases for reading/writing configurations from and to the
radio with the third-party software
- Intercept the serial data streams at either the USB driver level
or the RS-232 serial link level (it's my understanding that this radio does indeed use RS-232 levels and async serial communications). Wireshark and logic analyzers are my friends!
- Analyze the serial data streams for this radio and compare them to
samples of known Yaesu programming protocols for other models (I believe they tend to re-use the same protocol for many models)
- Compile and run test builds of a modified Chirp build from a Git
repo and test them
Here's what I would need help with:
- Someone familiar with Python, the Chirp drivers, and ideally
Yaesu's programming protocols, to work on the Python code to adapt an existing Chirp driver for the FTM6000.
Is there someone on the list who would be interested in working with me on adding support for this radio to Chirp?
Regards, Steve Hersey
-- Steve Hersey N1XNX n1xnxham@gmail.com
"Any sufficiently advanced technology is indistinguishable from magic." -- Clarke's Third Law "Any technology distinguishable from magic is insufficiently advanced." -- Benford's Corollary "Any sufficiently advanced magic is indistinguishable from technology." -- Charles Stross, *Dead Lies Dreaming* “It's still magic even if you know how it's done.” -- Terry Pratchett
-- Steve Hersey N1XNX n1xnxham@gmail.com
"Any sufficiently advanced technology is indistinguishable from magic." -- Clarke's Third Law "Any technology distinguishable from magic is insufficiently advanced." -- Benford's Corollary "Any sufficiently advanced magic is indistinguishable from technology." -- Charles Stross, *Dead Lies Dreaming* “It's still magic even if you know how it's done.” -- Terry Pratchett _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to sandhillsinvestment@gmail.com at sandhillsinvestment@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Steve Hersey at n1xnxham@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
I think I'm going to give up on this effort and just use the RT Systems stuff I've already purchased. I have a working serial port tap using a Saleea logic analyzer, and I've been able to capture comms traffic during a "clone TX" from the radio. I've determined that it uses 38400 bps and 0x06 as an "ack" (suggesting commonalities with other Yaesu radios).
Beyond that, I cannot make any sense of the various chirp Yaesu drivers, decipher the data path through the code, or determine anything at all about what the protocol framing of any of those radios is supposed to look like, so I'm not able to compare it with my captured data or identify the memory size it uses. Nor have I been able to find any descriptions of likely Yaesu comms protocols or memory layouts online. Without more information, this task requires better Python skills and far more familiarity with chirp drivers than I possess, so I'm stopping here.
I continue to appreciate the effort folks are putting in to support radios on this software.
Regards, Steve
participants (2)
-
Jeffrey Vian -
Stephen Hersey