[chirp_users] Support request - Yaesu FT-1500M
There have been multiple requests for Yaesu FT-1500M support besides my own. Was a radio ever sent in for testing? I am willing to send in mine if you provide instructions to do so.
From Dan almost 4 years ago:
Changes (by kk7ds): * owner: => kk7ds * status: new => accepted Comment: Happy to add this as soon as someone can loan me a radio :)
http://intrepid.danplanet.com/pipermail/chirp_users/2011-August/001295.html
I do not yet have the official programming software for this radio to provide. There are a couple of other radios that are already supported by Yaesu that have at least the same programming cable. Hopefully that helps a bit.
Andrew Harmon KD5RKO
There have been multiple requests for Yaesu FT-1500M support besides my own. Was a radio ever sent in for testing? I am willing to send in mine if you provide instructions to do so.
From Dan almost 4 years ago:
Changes (by kk7ds):
- owner: => kk7ds
- status: new => accepted
Comment: Happy to add this as soon as someone can loan me a radio :)
I'm not really looking to wrestle with more yaesu mobiles at the moment, so perhaps I should change the status of that bug :)
That said, there are other chirp developers that may very well be interested. Indicate your offer of a loan on that request tracker if you haven't already and maybe someone will be interested in picking it up.
--Dan
Thanks for the reply Dan. So if I update the request, theoretically someone will want to try it out? If I had some programming skills, I would give it a shot myself. I'm planning on trying some of the existing Yaesu mobile profiles to see if it can at least download data. If I can not get anybody to bite on a loaner radio to work with, how would I go about trying to develop my own driver for it? I'm thinking about buying the RT Systems software at this point, which I have already purchased for my FT-60. If there is anything I can do to add this radio to the stable of supported radios, I would certainly do it.
Who are the other chirp developers? And how do I become one myself?
Thanks again for all the work you do!
Andrew Harmon
On Wed, Apr 15, 2015 at 10:05 AM, Dan Smith dsmith@danplanet.com wrote:
There have been multiple requests for Yaesu FT-1500M support besides my own. Was a radio ever sent in for testing? I am willing to send in mine if you provide instructions to do so.
From Dan almost 4 years ago:
Changes (by kk7ds):
- owner: => kk7ds
- status: new => accepted
Comment: Happy to add this as soon as someone can loan me a radio :)
I'm not really looking to wrestle with more yaesu mobiles at the moment, so perhaps I should change the status of that bug :)
That said, there are other chirp developers that may very well be interested. Indicate your offer of a loan on that request tracker if you haven't already and maybe someone will be interested in picking it up.
--Dan
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Apr 15, 2015 at 8:05 AM, Dan Smith dsmith@danplanet.com wrote:
That said, there are other chirp developers that may very well be interested. Indicate your offer of a loan on that request tracker if you haven't already and maybe someone will be interested in picking it up.
I've added support for a number of Yaesu radios, and theoretically, I wouldn't mind taking this one on too. The trouble is I'm afraid it would sit untouched on my workbench for months while I tried to find the time to do it. That really wouldn't be fair to the owner.
Trying to download with an existing Yaesu driver is one of the first things I would try. If the one you pick has the same baud rate, you'll get at least a partial image download. This will undoubtedly fail to decode, showing lots of errors in Chirp, but you will be able to save it and inspect it with a hex editor. The next step is subjective--it's not too hard to spot a repetitive section in the data that are the list of channels. Now you can start modifying the existing Chirp driver (after duplicating it) to decode the section of memory you've identified.
There's more information about becoming a developer here: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Further discussion like this should take place on the chirp_devel list.
Tom KD7LXL
participants (3)
-
Andrew Harmon -
Dan Smith -
Tom Hayward