-
Notifications
You must be signed in to change notification settings - Fork 99
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
netlist #713
Comments
Do you have a sample file? |
I have the same issue in the config: |
Using DIYLC 4.37.0 As a test, I created a very simple KiCAD (6.0.11) schematic, and generated a netlist (see below). When I tried to import it into DIYLC, I got the following dialog: and then clicking Ok, not a lot happened. TBH, I am not sure what is meant to happen. Log file:
Test Netlist file
This was the test schematic Maybe the schematic was bad, or too simple. I can provide a better test if required. |
Hi @bancika, @greenonline, I've had the same problem with my Kicad schematic I've created and exported as a netlist. The schematic passes the Electrical Rules Checker (ERC) in Kicad so it should be valid. I'm new to kicad/diylc so I'm a novice using both tools and may have made a mistake somewhere. Software: @greenonline, Do you have the original KiCad schematic file to check if it's valid? @bancika, Another question, how do I export the netlist from a diylc layout directly to a file? The only way I found I could do it was by File -> Analyze -> Generate DIYLC netlist (*) which opens a window with the netlist text. I then manually copy-paste the text into another text editor and save the file. However, when I try to import the netlist created by diylc back into a new diylc instance, no parts are found. It is the same problem as described previously. I looked for some documentation on this, but could not find anything obvious. |
DIYLC supports LTSpice netlist format at the moment, not KiCad
@JustGitting use "Generate Spice Netlist" feature as DIYLC netlists are my
internal format that is used for some other features under "Analyze" menu
Cheers.
…On Sun, Nov 19, 2023 at 5:49 AM JustGitting ***@***.***> wrote:
Hi @bancika <https://github.com/bancika>, @greenonline
<https://github.com/greenonline>,
I've had the same problem with my Kicad schematic I've created and
exported as a netlist. The schematic passes the Electrical Rules Checker
(ERC) in Kicad so it should be valid.
I'm new to kicad/diylc so I'm a novice using both tools and may have made
mistake somewhere.
Software:
DIYLC V4.37
Kicad V7.0.
@greenonline <https://github.com/greenonline>, Do you have the original
KiCad schematic file to check if it's valid?
@bancika <https://github.com/bancika>,
There seems to be variations in netlist formats across applications (
https://electronics.stackexchange.com/questions/1674/is-there-a-common-netlist-format).
What file format does DIYLC expect for a valid netlist files?
Another question, how do I export the netlist from a diylc layout directly
to a file?
The only way I found I could do it was by File -> Analyze -> Generate
DIYLC netlist (*) which opens a window with the netlist text.
I then manually copy-paste the text into another text editor and save the
file. However, when I try to import the netlist created by diylc back into
a new diylc instance, no parts are found. It is the same problem as
described previously.
I looked for some documentation on this, but could not find anything
obvious.
—
Reply to this email directly, view it on GitHub
<#713 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXONCJJTYFRZZVVPJZECG3YFGFUDAVCNFSM52P5XNQ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRG43TINBYGM2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Branislav Stojkovic
www.diy-fever.com
|
Thanks @bancika for the clarification. Is the feature to export Spice netlists to a file on the roadmap? |
How can I import .net file ?
I've tried "File"-> "Import Netlist" and select .net file created by LTSpice XVII but no components are detected.
What kind of format is available ?
The text was updated successfully, but these errors were encountered: