Project

General

Profile

Actions

Bug #4251

closed

Yaesu FT-7800R and Yaesu FT-7900R

Added by James Carey about 8 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/22/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

There are problems with the csv file format generated by RT Systems software prohibiting it to be successfully imported into Chirp. So far I have identified the following issues:

RT Systems csv file's header values are not recognized during import and the file contains random extraneous quotation marks in the Comment field's Values.

Result: The file will appear to import with out error but no data will be present. In other words, Chirp does not produce an error after import despite the fact that no data appears to be imported from the RT Systems CSV file.

Recommendation: Chirp produce an error informing the user that no data has been imported and that the CSV file is corrupt.

Side note: I am attempting to repair the RT Systems CSV file by removing the extraneous and changing the Field names to something Chirp should be able to recognize. Will let you know if I am successful.


Files

Yaesu FT-7900R 2016-11-22.csv (194 KB) Yaesu FT-7900R 2016-11-22.csv James Carey, 11/22/2016 09:17 AM
Actions #1

Updated by James Carey about 8 years ago

This is the original RT Systems CSV File

Actions #2

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Rejected

Chirp's CSV format is different to what RT Systems provide.
In other words, Chirp will not be able to import RT Systems CSV. That's valid for any radio.

Actions

Also available in: Atom PDF