Showing manf# as number in Excel

hildogjr / KiCost

Build cost spreadsheet for a KiCad project.

MIT License

496 stars 97 forks source link

Showing manf# as number in Excel #423

Closed sebo83910 closed 3 years ago

sebo83910 commented 3 years ago

Hello,

First of all, thanks for this nice piece of software. It's very useful! I'm using a csv bom file and version 1.1.15 of kicost. I'd like to report two specific parts for which the tool is unable to complete part search:

BAT54H,115: diode from Nexperia. If I replace the ',' by '-' it finds it but it's not the correct manf# information. I guess a simple regexp in the manf# parse could solve this issue.
9551670000000: DB9 connector. Excel somehow represents the number in exponential (9.55E+12) and fails to search.

Thanks. Sébastien

hildogjr commented 3 years ago

See section Parts With Subparts in https://xess.com/KiCost/docs/_build/singlehtml/index.html. The , is used to indicate multiple manufacture part numbers. If it is present a single part number, it must be preceded by escape character: \,.

The other issue, please attache a BOM example and the commands execute to call KiCost.

sebo83910 commented 3 years ago

github won't let me upload a csv file... :( here is the xlsx: github-issue423.xlsx

In the csv, here are the values used: manf#	refs
9.55167E+12	J6

The DB9 connector (Mouser ref) is 9551667812741 and I used this value within the csv file. Excel shows it in scientific mode.

sebo83910 commented 3 years ago

The command line is the following: python3 -m kicost -i github-issue423.csv --exclude arrow lcsc tme --overwrite

hildogjr commented 3 years ago

Is this spreadsheet generated by a CSV or XML file? I could not reproduce this on Linux-LIbreOffice.

Please, attach the file example (changing the extension for GitHub ignore it).

sebo83910 commented 3 years ago

Here it is. The file has been created with MS Excel 2016. github-issue423.csv.xlsx

set-soft commented 3 years ago

The problem here seems to be a wrong part number. The correct part number is "09551667812741", not "9551667812741". Using the correct value I get data from KitSpace API.

KiCost writes it as an string, I guess the "9.55167E+12" comes from some mistake when importing the CSV in Excel. I tried loading the KiCost XLSX in Excel from Office 365 and it shows the correct P/N.