Milton,

I have created the csv file from scratch using the proper syntax that chirp wants to see. It takes the first 16 lines of the csv file and then errors out on the rest. I cant see any syntax errors in the file at all.

Regards,

Anthony (N2KI)

On Tue, Sep 17, 2013 at 9:02 PM, Milton Hywatt mhywattt@yahoo.com wrote:

I think I saw some dialog in here regarding a similar error maybe a couple weeks ago. What is the source of the CSV file? Was it exported from source without an error? Can you import it into an Excel or other similar type document without error?

---

*From:* Anthony (N2KI) n2ki.ham@gmail.com *To:* chirp_users@intrepid.danplanet.com *Sent:* Tuesday, September 17, 2013 8:50 PM *Subject:* [chirp_users] Column Number Mismatch Error

Hi,

New to Chirp and trying to import a csv file. I get an error

"Column Number Mismatch on Line 17". It goes all the way to Line 113. Only the first 14 channels are imported into the software. Using Build latest daily build.

Thanks for your help.

Regards,

Anthony (N2KI)

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

On Tue, Sep 17, 2013 at 9:46 PM, Milton Hywatt mhywattt@yahoo.com wrote:

The dialog I saw was Jim Unroe and his insight on Excel creating too many commas and some thing about a bug. But I couldn't tell if Jim was trying to say Excel had the bug or Chirp. I could hardly believe it was Chirp but from working with SQL, Excel, CSV, and importing using ODBC drivers for files from one brand of business software to another since 1999, that I could say without much doubt that it is Microsoft's issue.

Yes Milton. It is most definitely an Excel bug. And what Excel does is drops commas. This shifts the data from that point forward. Any software that imports CSV files would probably have problems with a file corrupted in this fashion.

Jim KC9HI

Jim,

EXACTLY! That was the problem. I opened it with Notepad and immediately saw the truncated commas. I added them in and it imported perfectly. Thanks for the feedback.

0,SIMPLEX,147.495,,0,Tone,136.5,136.5,23,NN,FM,5,,,,, 1,SIMPLEX,146.58,,0,Tone,136.5,136.5,23,NN,FM,5

Regards,

Anthony (N2KI)

On Tue, Sep 17, 2013 at 9:14 PM, Jim Unroe rock.unroe@gmail.com wrote:

...

"Column Number Mismatch on Line 17". It goes all the way to Line 113. Only the first 14 channels are imported into the software. Using Build latest daily build.

I'll bet you edited the CSV with MS Excel. It has a bug that doesn't like

all of the commas (,,,,) from empty fields at end of a row so it throws some of them away. As soon as CHIRP get to a truncated row, the fields become out of position with their columns.

You might be able to repair the CSV using a TXT file editor or a CSV file editor.

Someone in the UV-5R group had this issue and I suggested that he put something, anything, in the "Comment", "URCALL", "RPT1CALL", "RPT2CALL" columns. He said that worked perfect. Even a pair of quotes ("") might be all that is needed to do the trick.

Jim KC9HI

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

I had same problems like that, so between the groups of channels I put empty for spacers in the name banks  and to fill the banks between changes. I have tried different changes with the export to CSV, this worked. So fill in ALL the blanks, or should I say banks. :) No problems since. Alan

________________________________ From: Jim Kennedy jimkennedy@hawaii.rr.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Tuesday, September 17, 2013 8:43 PM Subject: Re: [chirp_users] Column Number Mismatch Error

I also had this problem (using EXCEL). Thanks for this discussion, explanation, and interim work around.

I have also had problems with the intermediate display in Export, which seems to give one the option of rearranging the channel numbers before saving.  It also seems to work on the first so-many lines (16?, I don't recall), and then does weird things after that.

Perhaps this is also caused by the same issue in EXCEL.

73,

Jim K6MIO/KH6

On Sep 17, 2013, at 3:14 PM, Jim Unroe rock.unroe@gmail.com wrote:

...

"Column Number Mismatch on Line 17".  It goes all the way to Line 113.  Only the first 14 channels are imported into the software.  Using Build latest daily build. I'll bet you edited the CSV with MS Excel. It has a bug that doesn't like all of the commas (,,,,) from empty fields at end of a row so it throws some of them away. As soon as CHIRP get to a truncated row, the fields become out of position with their columns.

You might be able to repair the CSV using a TXT file editor or a CSV file editor.

Someone in the UV-5R group had this issue and I suggested that he put something, anything, in the "Comment", "URCALL", "RPT1CALL", "RPT2CALL" columns. He said that worked perfect. Even a pair of quotes ("") might be all that is needed to do the trick.

Jim KC9HI

_______________________________________________

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users