-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KiCost 1.1.4, KiCAD 5.1.6-1 Install error under Windows 10 Pro x64 #421
Comments
Related with #412 We are right with low people number to fix all the issues. You still can use by the CLI commands: Also, try to install using |
I understand not enough people/hours in day to fix things... Tried pip kicost and easy_install kicost. Both say everything is fine, then KiCost doesn't work. KiCAD and the schematic in eeschema look great on both systems. I tried kicost -i PicoTAP.xml and end up with a spreadsheet containing BOM information, but not part vendor/cost information from distributors.
I just tried kicost under Ubuntu 16.04 LTS. Similar if not the same problems:
KiCost seems an important enough feature that I wonder if you could convince the KiCAD development team to support KiCost, kind of like Thunderbird did with Lightning calendar? KiCost is just as, if not more important, than 3D viewing. KiCost ranks up there with DRC and Annotation in my book. |
The first error appear that kicost is not recognizing your manucture code field. Did you fill some "manf#" field at Eschema? For now KiCost don't automatic identify parts second #17 . |
Kicost support some distributors and right now depends on KiSpace service or Octopart account. I think it dependency doesn't fill on KiCad idea. |
I think I am seeing the same error of macOS:
kicost --info:
|
I am however able to run it from the command line:
Are those queries returning "No information found" specific to a vendor or does it mean no info from any vendor? Each part has a Digikey PN already so I will need to investigate why I am seeing the query problem. |
Some problems can happens when the manufacture name on schematic is slightly different from real one (Vishay/vishay). I just catch in your log:
Have a look on #416 |
Yeah, that line is weird. There are actually two lines in the generated excel file:
I am not sure why. Those parts are single "gate" devices. So, one part per package. Looking at the line in the excel file seems to suggest that there are multiple parts per device package? |
#416 (comment) will solve it. |
Duplicated of #412 |
@hildogjr Yeah, I see that now. You can escape the comma with a backslash. I was wondering if that comma was going to cause a problem somewhere ;-) Thank you. |
The comma is intended to create parts will "multiple parts", useful for connectors and other assembled parts. |
Unfortunately, that creates a problem when using the other BOM tools ... they do not seem to recognize the escape and so the back slash is included the part number. |
Seems like a KiCAD issue. |
Other BOM tools will also not recognize the multiple part system. So, maybe, que KiCost need some improvements in this cases. |
Ah, ok. So, the comma in the part name is a KiCost feature, not an issue with KiCAD itself. Maybe KiCost could use a dedicated field for this purpose instead of using the part number? |
Questions:
I made this feature some (long) time ago, maybe there is a better way but I am too biased to put a opnion. |
The user could specify the field with a command line parameter? Something like "--multipartfield" or something that makes sense. I'm not too familiar with the feature so do not have a good suggestion on exactly what to call it. Is there a kicost.ini file? The KiBOM guys use an ini file for configuration of the tool for the project. So, for instance, you specify which field to use for the "do not fit" field in the ini file. They also use a field for linking to a part on the Digikey website. I've included a portion of the ini file below. The fit_field option in this example is "Config". I think the feature would work the same way you do it now. I do not see any need to change the functionality. Just use a custom field specified by the user.
|
This INI file was a good propose in the past. KiCost started to require a lot of parameters (in not straightforward use). In that time, I made the GUI (with memory of the parameters). But it is now broken. |
If one could ignore the "do not fit" components, that would be helpful as well. Or better yet, use a different field for "do not cost" and these components would be ignored and not included in the spreadsheet. |
The first already exists |
I misunderstood that --ignore_fields just ignored the field, not the entire part? What I want to do is ignore the part (leave it out of the spreadsheet entirely). Things like "fiducials" are "parts" on the PCB but are not real parts. Mounting holes is another example of "parts" that I would prefer are not in the BOM. |
Yes, correct just the field. But ignoring the DNP/NOPOP (filed used for not populated information yours), the part will be listed in the spreadsheet. |
Yes. NOPOP / DNP fields as 1. |
Saw the KiCost video, was really excited until I ran into problems I don't know how to solve in the Python environment. Help is requested.
After installing KiCost 1.1.4, KiCost won't start.
KiCost 1.1.4 won't start.
During install I see lots of
MS Windows 10:
Fresh install of KiCAD 5.1.6-1, then open CMD Window as Admin:
How to reproduce:
Fresh install of KiCAD followed by fresh install of KiCost:
Issue / Problem report
kicost --version
at terminal.--debug
option on KiCost call;kicost -w -i %YOUR_FILE% --debug 8
The last thing I could think to try is using pip to install:
This is a new design created using KiCAD 5.1.6-1 under Windows 10. Schematic done, aiming for PCB layout.
I'm stumped. Any help to get KiCost running will be appreciated. KiCost looks like a really amazing time saver.
The text was updated successfully, but these errors were encountered: