Good day everyone!
As fas as I know the famous radio programming tool CHIRP doesn't support this radio, yet. I have managed to read my FT-270 with CHIRP by selecting VX-170 from the dropdown menu. Will I expirience any issues after I upload the image back to the FT-270 radio?
Thanks.
On Tue, May 5, 2015 at 8:18 AM, YL3IM yl3im@ham.lv wrote:
As fas as I know the famous radio programming tool CHIRP doesn't support this radio, yet. I have managed to read my FT-270 with CHIRP by selecting VX-170 from the dropdown menu. Will I expirience any issues after I upload the image back to the FT-270 radio?
With little information, there is no way for me to say for sure, but my guess is, yes, you will experience issues uploading to an unsupported radio.
When I add support for a new radio, I analyze the data stream bit-for-bit to make sure I understand everything that is being transferred. Then I write the Chirp driver so that what it sends to the radio is indistinguishable from what is sent by the manufacturer's software or a clone from another radio.
It doesn't sound like you have done any analysis of the data from the FT-270, so writing to it would be just a guess, risky business.
Tom KD7LXL
| > As fas as I know the famous radio programming tool CHIRP doesn't support this radio, yet. | > I have managed to read my FT-270 with CHIRP by selecting VX-170 from the dropdown menu. | > Will I expirience any issues after I upload the image back to the FT-270 radio? | | With little information, there is no way for me to say for sure, but | my guess is, yes, you will experience issues uploading to an | unsupported radio. | | When I add support for a new radio, I analyze the data stream | bit-for-bit to make sure I understand everything that is being | transferred. Then I write the Chirp driver so that what it sends to | the radio is indistinguishable from what is sent by the manufacturer's | software or a clone from another radio. | | It doesn't sound like you have done any analysis of the data from the | FT-270, so writing to it would be just a guess, risky business.
Thanks for your answer, Tom.
Actually, the imported chirp data (at least the memory channels) looks legit. I am rather concerned about the Settings data. I could upload the .img file if this helps.
On Tue, May 5, 2015 at 10:53 AM, YL3IM yl3im@ham.lv wrote:
Actually, the imported chirp data (at least the memory channels) looks legit. I am rather concerned about the Settings data. I could upload the .img file if this helps.
You are free to do what you like with your radio. Here are some things I would verify before writing to my own radio:
- number of channels match VX-170 - all channel bit fields match (not just frequency and tone, or whatever else you can see in the spreadsheet editor. Use "show raw memory" and/or a hex editor to view the channel data.) - channel enable/scan/priority/etc flags match - total size of .img matches (you will need to modify the driver to request more data to verify this)
Tom KD7LXL
participants (2)
-
Tom Hayward -
YL3IM