5 ms·
There are quite a few components so common that people refer to them only by their part number (ESP8266, 555, WS2812, etc) - are you planning to support things
by ReverseCold 8y ago
There are quite a few components so common that people refer to them only by their part number (ESP8266, 555, WS2812, etc) - are you planning to support things like that too?
Right now it looks like only common/standard parts are parseable (resistors, leds, etc).
- kasbah 8y agoI think once you are entering actual manufacturer part numbers you are better off deferring this to a parts database or search engine. In my uses I have been deferring this to an Octopart search. You can see this working on e.g. https://bom-builder.kitspace.org https://bom-builder.kitspace.org (enter something into the description field and click around on the wand icons). We are planning to include standard part naming schemes such as Pro Electron [1] and JEDEC [2] to recognize common diodes and transistors where it makes sense. The more interesting approach to me is to actually try recognize transistor descriptions such as "npn sot23 125mW beta=200 ic>=200mA". There is some work in progress, by dvc94ch, for both approaches (if I recall correctly) on the antlr branch: https://github.com/monostable/electro-grammar/pull/4 https://github.com/monostable/electro-grammar/pull/4 [1]: https://en.wikipedia.org/wiki/Pro_Electron https://en.wikipedia.org/wiki/Pro_Electron [2]: https://en.wikipedia.org/wiki/JEDEC https://en.wikipedia.org/wiki/JEDEC
- dantle 8y agoYou did a nice job with capacitors. It was cool to write X7R and have it show up as a characteristic.
- gh02t 8y agoThat gets pretty fuzzy, though. For example, does ESP8266 refer to the actual chip itself (unlikely, at least in a hobbyist context) or one of the variety of modules? These general designations aren't really referring to specific parts, so much as classes of parts. That's probably not so useful here, given that this looks to be focused on parsing BOMs for ordering purposes.