Content-Length: 219986 | pFad | http://github.com/qeda/qeda/issues/5

94 Additional links (Feature request) · Issue #5 · qeda/qeda · GitHub
Skip to content
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

Additional links (Feature request) #5

Open
Gasman2014 opened this issue Sep 19, 2016 · 3 comments
Open

Additional links (Feature request) #5

Gasman2014 opened this issue Sep 19, 2016 · 3 comments

Comments

@Gasman2014
Copy link

Would there be any interest in adding an optional SPICE model within the library or an option to link to an external SPICE model (now that KiCAD is offering built-in simulation...)?

Similarly, any plan to provide links to .STEP models for MCAD?

@shamil-ru
Copy link
Contributor

There is no problem to add link to SPICE model, but that is a question how to use it because I did not use SPICE modeling in KiCad. I will investigate this option, thanks for idea.

Regarding adding 3D-models, this work is scheduled. 3D models are planned to be generated automatically for standard packages. As far as I know supporting of STEP models instead of VRML is added to KiCad dev-branch only. My plan is to add 3D models support after QEDA become cloud service (this is a next big milestone planned).

@Gasman2014
Copy link
Author

I think the SPICE modelling is currently still in dev but it was announced as in the roadmap a couple of months back and I think it is a compiled option from source - see https://youtu.be/A2_-hdRcf4U . Presume it is just Eeschema -> SPICE netlist. Would have though that being able to hook into a SPICE model embedded in the component itself might be quite a good feature. SPICE models are also quite small text files so should not be too storage dependant.

Regarding 3dStep models; I think you are right - native .step support is also still in dev but you can use .step models with the help of a couple of macros in FreeCad - have a quick look at https://forum.kicad.info/t/kicad-stepup-new-exporter-for-3d-mcad-feedbacks-are-welcome/1048/38
The requirements are that there are matched .wrl/.stp pairs of identically named models e.g. C_1206.wrl and C_1206.stp and there is a bit of adjustment necessary to ensure the scale and placement correspond. Interesting links there also to the parametric housing builder script for various style packages. Think this is something that could easily be incorporated but .step models can be big!!

Library management in KiCad is desperately needing something like this.

On 19 Sep 2016, at 21:49, Shamil Yakupov notifications@github.com wrote:

There is no problem to add link to SPICE model, but that is a question how to use it because I did not use SPICE modeling in KiCad. I will investigate this option, thanks for idea.

Regarding adding 3D-models, this work is scheduled. 3D models are planned to be generated automatically for standard packages. As far as I know supporting of STEP models instead of VRML is added to KiCad dev-branch only. My plan is to add 3D models support after QEDA become cloud service (this is a next big milestone planned).


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #5 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AIAyuW4aIxl2yEm1SRvlOBRUKRUKVECdks5qrvVngaJpZM4KA1jw.

@shamil-ru
Copy link
Contributor

Interesting information, thanks a lot. Will examine it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/qeda/qeda/issues/5

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy