Eagle 7.6.0 and LTspice

[e.arckens]

I find it unbelievable how this company still is not able to get what is a major selling point to work at all. After 2 years of forum discussions, here and anywhere on the internet I have not found one single user who was able to get it to work. What is worse, even your own paid employees are not able to solve this problem.

My situation:

1. Eagle 7.6.0 in default directory

2. Eagle libraries installed, including a subdirectory in lbr for ltpsice which includes lt-spice-simulation.lbr

3. LTspiceIV.exe and LTspiceVII.exe available in Eagle bin directory, in their own directories under root C:\Program Files (x86)\

4. In "options/directories" all relevant directories are installed

Even your own "example/ltspice/3518-eagle.sch" is not able to connect to LTspice (CAP.asy does not exist as LTspice symbol), some cryptic message about "open library and eviceset, and export device"..

And LTspice works even less when trying to use it with my own schematics.

I hope at least someone here is able to provide a lasting and working solution, so that rumours do not have to start about the buncb of amateurs working in this particular section of Eagle/Autocad.

[e.arckens]

Forgot to say: Windows 7 64b

[jorge_garcia2]

Hi @e.arckens,

Thanks for participating on our forums. I totally hear you since I'm one of the employees who worked on the effort to update the LTSpice ulps. Now I can assure you that there is a very good reason why development has basically ceased on that ULP and as a plus I have been authorized to give a sneak preview of that feature. See the pictures below, this is slated to be released within the next week or so.

Let me know if you have any questions.

Best Regards,

[e.arckens]

I do not see the point in this supposed answer to my question.

Clearly an obfuscated way of communicating that LTspice is not worth the time at autocad.

[matt.berggren]

Thanks for your reply. Just to be clear – punching out to a 3rd party simulator is not ideal. If they change the tools or we change the tools, we need to do an awful lot of work to try and keep this up. This is why we included SPICE in the SW directly in this next release. We don’t own the LT SPICE development schedule and they do not build around EAGLE’s timelines. This is pre-Autodesk behavior and was a way of delivering SPICE simulation without doing the hard work of serious integration. We’d (Autodesk) like to develop around the things that we can control. That said, the SPICE engine going into 8.4 is ngSPICE-based (a wrapper around Berkeley 3f5 and prior) & with much tighter integration. LT has not been maintaining the LTSPICE link in EAGLE and we have taken a different path to deliver better functionality that is more tightly integrated. To be sure, it cost us more development time / energy but with a better long-term outcome.

Hope that’s clear!

Best regards,

Matt – Director, Autodesk EAGLE.