Needing more than a spark test?

[graham-xrf]

@graham-xrf I don't seem to have an Autogenerated subdirectory under sym. I can create this, but is it necessary?
Under home, it is .wine/drive_c/users/bruce/My Documents/LTSpiceXVII/lib/sym as I said, there's no Autogenerated . First folder is ADC. I have display hidden directories ON.

Not to worry. That one comes about if you have the .lib file in the LTSpice editor, and you right click on the SUBCKT name of the part, and it pops up a box asking if you want to "autogenerate" a default symbol with the right number of pins to use in the circuit. Once in, yo can edit it, move the pins about, etc. and save.

I already went through all that, and I dumped the yellow box symbol, and drew lines and stuff to make an op-amp.

You very likely only need to create the Autogenerated folder in the right place, and put the symbol I made into it.
There are several YT videos about doing this stuff. Look in the text file here. It also has hints.

I know you went looking under .win/drive_c path, but notice that it uses a symlink to point you back to your home folder.
Open your home folder, then look in Documents, and see LTSpiceXVII.
My path was /home/graham/Documents/LTspiceXVII/lib/sym/AutoGenerated
My Linux happens to be Linux Mint, which is Ubuntu-based, but I think all Linux distros have a Documents folder.

 

[WobblyHand]

Well I did as indicated above and have received a very strange error.

Umm, as far as I know, this path does not exist in my system!

The spice error log says:
Fatal Error: Could not open library file "Z:\data\LM20\Engineering\XRF-Materials Analysis\LTSpice Simulations\pin diode TIA amps\TIA-LMC662\LMC662C.lib"

I don't seem to have a working help file any more. This alleged upgrade might not be complete.

 

[graham-xrf]

@WobblyHand
Bruce - let's get this working on something simple. What Linux distro do you have?
I think the fact you got the messages you show indicate all is well.
Except for - it's looking for a drive Z ??
It may be you have to look for the .lib text in the Spice directive on the schematic, right click it, and select that it is a .lib, and not a .inc choice

 

[homebrewed]

I would like a copy of the script. I believe FreeCAD can import SCAD. If not, I'll install it. From that I can get a better idea of what to do.

I ordered 8 sources from China. About $1.54 each plus shipping.

It's attached. Fortunately .scad files were recently added to the permitted file-types list.

 

[WobblyHand]

@WobblyHand
Bruce - let's get this working on something simple. What Linux distro do you have?
I think the fact you got the messages you show indicate all is well.
Except for - it's looking for a drive Z ??
It may be you have to look for the .lib text in the Spice directive on the schematic, right click it, and select that it is a .lib, and not a .inc choice

An Ubuntu derivative called Pop!OS. I have nothing on my system that remotely has paths like that. I have one disk on my system, no other devices are plugged in. Right clicking shows me:

I clicked Ok, since that's right. I changed the abs V tol to 1nV and abs I tol to 1pA in Control Panel. I am using TIA-LMC662C-2.asc as the schematic.

In the Spice tab of control panel I have:
Gmin = 1e-12
Abstol= 1e-12
Reltol = 0.001
Chgtol = 1e-14
Trtol = 1
Volttol = 1e-6
Sstol = 0.001
MinDeltaGmin = 0.0001

Default Integration Method: modified trap
Engine: Normal

If I open TIA-LMC662C-1.asc, the simpler file, I get identically the same library error. I have no idea where this path is, or how it got there.

If I open an existing file and use the windows navigator, I find that Z: is my root disk! But there is no Z:/data in my system! This is a bug, and it is the path of an LT person, who developed the code, or something like that...

I opened a five stage analog filter that I create three years ago, using an OPA365, and LT6237 and it simulates fine. I have imported the OPA365 model using a simple .inc OPA365.MOD statement. So my SPICE isn't totally broken, but there maybe something odd with the asc file? What version of LTspice are you running?

 

[WobblyHand]

It's attached. Fortunately .scad files were recently added to the permitted file-types list.

FreeCAD doesn't support importing this file, which is too bad. So I installed OpenSCAD so I could take a look. The view that initially rendered was small and I didn't know what I was looking at - just a flat plate. I zoomed in and could see what was there. I have a better idea of the concept now.

@graham-xrf did you ever fix your FreeCAD model?

 

[graham-xrf]

FreeCAD doesn't support importing this file, which is too bad. So I installed OpenSCAD so I could take a look. The view that initially rendered was small and I didn't know what I was looking at - just a flat plate. I zoomed in and could see what was there. I have a better idea of the concept now.

@graham-xrf did you ever fix your FreeCAD model?

Hmm - I am thinking to get to it next. I got distracted by digging into the Pocket Geiger thing.

 

[graham-xrf]

I opened a five stage analog filter that I create three years ago, using an OPA365, and LT6237 and it simulates fine. I have imported the OPA365 model using a simple .inc OPA365.MOD statement. So my SPICE isn't totally broken, but there maybe something odd with the asc file? What version of LTspice are you running?

This is good. It at least works! BTW I see LTSpice in .wine does use a Z: drive
You should be able to treat the .asc file for the LMC662C just like your filter from 3 years ago.
You might create a new folder just for the LMC662 circuits if you like.
The LMC662C.lib file is put in the same folder, and one can use the same include, as in .inc LMC662C.lib.

The original .MOD file is with the TI data, but that is not the issue. It would have to be edited to have the SUBCKT have the matching part name.
It does not matter what the filename is, nor the extension, so long as the correct name and (and path if necessary) is in the Spice include directive
BUT
Just using .inc raw like that can cause problems unless you know it is compatible with what you have already in the circuit, in that it does not have any duplicate names or numbers in there. Things like "V3". For an imported model, the circuit will have the inevitable duplicate nodes, and it's a pain to go through a big model file renaming or renumbering those that clash.

Here is where a .inc gets help. The fix is to right-click on the .inc Spice directive statement on the drawing. In this case, it's already done, so you see a .lib directive instead, but you can right-click on the .lib directive anyway, and make sure it has the correct radio button selected.



Choose the SPICE .lib button. This is not about the file extension.
It just lets LTSpice use the file as if it was like any other library file, without getting in a knot about duplicate names. It turns the .inc into a .lib directive.

I think you are nearly there. If you can simulate the past filter, you should be able to get this going without having to re-draw the whole thing.

 

[WobblyHand]

This is good. It at least works! BTW I see LTSpice in .wine does use a Z: drive
You should be able to treat the .asc file for the LMC662C just like your filter from 3 years ago.
You might create a new folder just for the LMC662 circuits if you like.
The LMC662C.lib file is put in the same folder, and one can use the same include, as in .inc LMC662C.lib.

The original .MOD file is with the TI data, but that is not the issue. It would have to be edited to have the SUBCKT have the matching part name.
It does not matter what the filename is, nor the extension, so long as the correct name and (and path if necessary) is in the Spice include directive
BUT
Just using .inc raw like that can cause problems unless you know it is compatible with what you have already in the circuit, in that it does not have any duplicate names or numbers in there. Things like "V3". For an imported model, the circuit will have the inevitable duplicate nodes, and it's a pain to go through a big model file renaming or renumbering those that clash.

Here is where a .inc gets help. The fix is to right-click on the .inc Spice directive statement on the drawing. In this case, it's already done, so you see a .lib directive instead, but you can right-click on the .lib directive anyway, and make sure it has the correct radio button selected.

View attachment 434397

Choose the SPICE .lib button. This is not about the file extension.
It just lets LTSpice use the file as if it was like any other library file, without getting in a knot about duplicate names. It turns the .inc into a .lib directive.

I think you are nearly there. If you can simulate the past filter, you should be able to get this going without having to re-draw the whole thing.

So close, yet so far... Seem to be missing something. Still getting the same error. For this part you say, choose the SPICE .lib directive? And then what? We have 3 possible button choices. Is it OK? If so, then I get the same error. If Open, it opens up the LMC662C.lib file, which seems ok. If Browse, I can choose the file, LMC662C.lib.

Must have made a mistake at an earlier step, perhaps with the sym/AutoGenerated directory or something else.

I'm not sure I have a fully updated copy of LTspice. If I sync release, it seems to download the same few things and stops. If I do it again, it seemingly finds the same files to download. I also don't have help files anymore. What's the latest LTspice that works on Linux?

 

[graham-xrf]

My LTSpice is LTspice XVII(x64) version (17.0.35.0)
When I first downloaded it as .exe I think, linux Mint automatically popped up and gave me the choice to have the Wine install happen.
When updates are ready, LTSpice just brings the pop-up to let one do the update.
It may be that before you do anything with LTSPIce updates, you do the update for Pop!OS

The download should complete. I am not sure what is happening there.
The text file attached in post #1231 has a bunch of YouTube links, which is where I learned the basic ways this can work.

One can actually drop an entire model file into the circuit drawing as a "comment", and have the simulation use it, because it ends up in the netlist.
This is yuk! It takes up lots of space, and clutters everything.

The exact same result can be had with .inc to "include" it, as if it was in the drawing.
Then, the way to make using it easy, is to use it as a .lib file.
I did not make the .lib SPICE directive directly. I started with a .inc include.
The .lib statement got made automatically when I clicked on the correct button choice.

I am suspicious of the update not completing. It may be better to get your previous designs stashed somewhere, and delete all trace .of LTSpice, and load up again. This means losing the c_drive in wine, and then also removing the LTSpice folder in /hjome/bruce/Documents. That said, I am wary, because that seems unnecessary if you can already make an old filter simulate.