CHIRP

I need to see your CSV file(s) in order to tell you what the problem was. Can you attach here please?

The problem is that the header has had the field (name)s quoted which causes chirp not to recognize it. Since these fields don't have spaces or special characters in them, they shouldn't be quoted. These are items 1 and 4 from CSV_HowTo.

Note the difference between the sample file (first line) and yours (second line):

-Location,Name,Frequency,Duplex,Offset,Tone,rToneFreq,cToneFreq,DtcsCode,DtcsPolarity,RxDtcsCode,CrossMode,Mode,TStep,Skip,Power,Comment,URCALL,RPT1CALL,RPT2CALL,DVCODE
+"Location","Name","Frequency","Duplex","Offset","Tone","rToneFreq","cToneFreq","DtcsCode","DtcsPolarity","RxDtcsCode","CrossMode","Mode","TStep","Skip","Power","Comment","URCALL","RPT1CALL","RPT2CALL","DVCODE"

The reason the message is vague is because the CSV driver didn't recognize it as a matching file at all, and thus didn't provide more detail (as it would have if there was an error on one specific line once it started processing it).

Let me also point out that once you fix that, you'll also find it fails to parse all of your channels since they all have errors related to having spaces for what should be empty strings. It will point this out (on every line) and then it will complain again about "unknown format" since it couldn't extract a single valid channel from the whole file. So things like your duplex and skip fields are " " when they need to be empty (or at least quoted empty "").

I've pushed a few related changes to the next build which should make our detection logic tolerate the quoted fields. I can't say I've seen that complaint in all the years we've been doing CSV files, but I'm assuming there's some opinionated spreadsheet application you're using that won't respect the input format or something. Hopefully that helps.

Dan,

Thanks for your help! I’m afraid I got tripped up by Apple’s fetish about “looking pretty” and I’m experienced enough to know better. I took my copy of the CSV file (I sent you) and dumped it out in the good ol' CLI Terminal program; sure enough, there were “". When you do a Preview of such a file on a Mac, they do not show the “". My bad.

You are correct below. Once I killed the “” the CSV file loaded into CHIRP but then registered messages that were easier to follow, and I made those corrections. [“...you'll also find it fails to parse all of your channels since they all have errors related to having spaces for what should be empty strings…]

Once all corrections were made, my CSV loaded into CHIRP just fine!

I again thank you for your quick attention to this. I’ve got my file into CHIRP; now onto the steps to get it into the radio. Keep up the good work.

R

On Sep 4, 2024, at 11:49 AM, Dan Smith redmine@chirpmyradio.com wrote: