On part detail pages, when a schematic symbol does not exist, there are buttons to 'Request' and to [sometimes] 'Build'. The 'Build' button starts the InstaBuild process; While not perfect, the InstaBuild process is both functional and nearly instant (minutes). Does anyone know why the 'Build' option is unavailable for some parts lacking schematic symbols (and if there is any way to trigger the InstaBuild process for parts lacking the 'Build' button)?
Added 6 years, 5 months ago.
Great question! The reason is that not all parts have datasheets that can be parsed by InstaBuild. For example, they might not include a pinout table. In these cases, we don't show the button so you don't waste time trying to make it work on a datasheet that's not compatible.
That being said, it's a great idea to make it initialize it outside of a part page. Will discuss with our team today and keep you posted!
Answered 6 years, 5 months ago.
I like the InstaBuild feature, too...
i say:
Even without a datasheet, it is much better, than typing everything oneself... :)
Can we remove that "compatible datasheet" rule?
Thx.
Answered 6 years, 5 months ago.
Hi Ricky, I've shared this feedback with our team and we have some ideas in terms of how we can remove the "compatible datasheet" rule. Will keep you posted here. We should have some updates on that soon.
Answered 6 years, 5 months ago.
BUMP!
Hey, all -- It's been 3 weeks since Ricky seconded my request and SnapEDA admin offered to look into it -- has there been any forward progress in allowing a manually triggered "instabuild"?
I've manually created dozens of components since my original posting, and each time I've wished for the ability to type in the pin/name table in SnapEDA's site -- sure, I can build up library components manually in Altium from scratch, but it still takes longer than a 'manual' instabuild where I would just type in the pin/name table.
Note that I've basically done the "manual instabuild" a few times anyway, when the algorithm detects a "compatible datasheet" and starts the instabuild process, and it turns out that the datasheet (which DOES have tables in it) doesn't necessarily have a table with pins/names in a useful format. When this happens, it's simple enough to manually enter the pin/name pairs line by line and then just generate the symbol. (I end up proofreading/fixing typos in the OCR'd pin/name table most of the time anyway, so manually typing each line just isn't a big deal.)
Thanks!
Answered 6 years, 4 months ago.
By the way, please let us know if you have any other suggestions to improve it. InstaBuild is a very new feature, so we're open to further feedback!
Answered 6 years, 5 months ago.
Hi All, I'm Mike, the product manager at SnapEDA. Just want to let you guys know that we're working on a standalone version of InstaBuild where you can build any part regardless of whether the datasheet is parse-able or not. We're aiming to launch this feature next week. I will let you guys know when it's ready. Thanks for your feedback!
Answered 6 years, 4 months ago.
Hey everyone, it's been about four months since these suggestions were made and the "announcement" was made by Mike (product manager), but there has been no update about the launch of this standalone feature. So what's going on? This would be a super useful feature!
Answered 6 years ago.
Also, another suggestion for the InstaBuild, it would be nice if you could add a NC (Not Connected) option in the tables column for "Pin Type"
Answered 6 years ago.