Bug #7561
closedCannot Read Radio or Radio Memory .dat Files Created with FT-3DR
0%
Description
FT-3DR shows as supported, but the .dat files generated by the radio cannot be read by Chirp. Upon attempting to open them Chirp indicates it cannot detect the type of radio, and manually selecting the type results in an empty table. No other method of importing and exporting FT-3DR data seems possible without an additional cable (whereas .dat files can be imported/exported on the radio's SD card).
Files attached.
Files
Updated by William Hirsch almost 5 years ago
I should note that CSV's from ADMS-11 cannot be opened in Chirp, and Chirp's CSV exports can't be opened in ADMS-11.
Updated by William Hirsch almost 5 years ago
appears to be an issue with the FT2D as well https://chirp.danplanet.com/issues/5579
Updated by Bernhard Hailer over 4 years ago
- Tracker changed from Bug to Feature
- Target version set to chirp-legacy
- Model affected changed from (All models) to Yaesu FT3D, FT2D
That's a feature request - Chirp can't do that yet.
Updated by Bernhard Hailer about 4 years ago
- Tracker changed from Feature to Bug
- Status changed from New to Rejected
- Platform set to Windows
Hi William, there are a number of misunderstandings here.
- Chirp often does not support native data formats. The .dat format is not supported.
- You need to connect the radio to a computer running Chirp using a cable, indeed - that's the intended way of using it. Then you can download data from it, modify it, and upload again.
- Although Chirp does support "CSV", it doesn't mean that it can read any CSV file arranged in arbitrary ways. Chirp expects the data in specific columns to be of a specific type. Chirp cannot read CSV files which aren't specifically formatted for it (see CSV HowTo.
- As far as I know, there isn't currently any radio within Chirp which supports programming via SD card.
You may want to open a Feature Request asking for implementation of .dat file import/export and operation through SD cards - but you might have to wait a long time for an implementation.