Project

General

Profile

Actions
Copy link

Bug #477

closed

CSV import on Build 20130129

Added by David Z almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Tom Hayward
Category:
-
Target version:
0.4.0
Start date:
01/29/2013
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
csv
Platform:
All
Debug Log:
I read the instructions above:

Description

I received a "No Channel found" response when I tried to import a CSV file created by a Yaesu VX5-R into build 20130129. I will attached a copy of the import file.

Files

Radio freq 012813.csv (17.2 KB) Radio freq 012813.csv David Z, 01/29/2013 03:59 AM

Related issues 1 (0 open — 1 closed)

Related to Feature #533: Support a wider range of CSV dialectsClosedTom Hayward02/09/2013

Actions
Actions
Copy link
 #1

Updated by Tom Hayward almost 12 years ago

  • Status changed from New to In Progress
  • Assignee set to Tom Hayward

This CSV format is dramatically different than the CSV format understood by Chirp. Most of the columns have different names and units. I'm working to see if I can decode it.

Actions
Copy link
 #2

Updated by Tom Hayward almost 12 years ago

  • Status changed from In Progress to Closed
  • Target version set to 0.4.0
  • % Done changed from 0 to 100
  • Chirp Version changed from 0.2.3 to daily
  • Model affected changed from (All models) to csv
  • Platform changed from Windows to All

You should now be able to read this style of CSV with Chirp (in latest daily build).

Actions
Copy link

Also available in: Atom PDF

Copyright 2023 CHIRP Software LLC