Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
No information about current state of KiCost #357
I really can't tell by looking at this repo, or at documentation, what the current state of KiCost is.
I have used it extensively in the past, for multiple boards, and now I need it again to update those boards.
I installed it using pip3 and got something that failed because I have no Octopart API Key, so I went to Octopart but it looks like they are issuing keys to developers of apps, and not end users. Is this true?
On top of that, it looks like KiCost is moving away from Octopart, judging from conversations in the issue tracker? It's hard to tell.
On top of that, I don't think scraping works any more?
If I am:
Is it possible to get a working version of KiCost? I absolutely love its output, and I have 5 boards where manf# etc are already filled in, and now I need some way to get usable BOMs.
If it is possible, could you add how to make KiCost work to the readme?
Hi. I'm glad KiCost helped you in the past. I wish it could help you now. But that probably won't happen.
We moved KiCost to Octopart because I had to continually change the scraping code to account for the changes in the web page formats used by each distributor (in addition, Mouser started using Distil which completely thwarted any scraping).
After three months, Octopart revoked my free license and wouldn't issue any licenses to anybody to use KiCost. They also stopped issuing free licenses to anybody but students. Octopart did offer to sell me a $1200 yearly license limited to 10,000 HTTP accesses per month, which I declined.
Now the plan is to move KiCost to using the Partinfo interface at kitspace.org. Partinfo will probably use some mixture of web scraping and distributor's public APIs to get pricing information (as well as a lot of other stuff). Up to now, I haven't been involved in this very much but I don't think it's functional.
So your current options are:
This all assumes you need pricing information. If all you need is a BOM, it would seem your old KiCost spreadsheets would still have everything you needed except current prices. And there are plenty of BOM tools for KiCad now.
I'm more involved in the Partinfo migration (into the KiCost main branch). It is not operational now because is missing finish the
The issues that need more help now is Windows issue #339 (more information in https://forum.kicad.info/t/bom-from-eschema/16536/37). This have been difficult to solve without help of Windows user / programmers.
The Octopart branch tree here have this workaround, if not detected any user KEY (and other small fixes).
I am just corned about release this, the implication about Octopart use term and that the users will stay inerts about the necessity of KiCost changes.