element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Problem Converting Eagle Symbols
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 0 replies
  • Subscribers 177 subscribers
  • Views 282 views
  • Users 0 members are here
Related

Problem Converting Eagle Symbols

Former Member
Former Member over 15 years ago

I'm having a problem running a User Language Program that converts Eagle

symbols into LTSpice symbols. The ULP is named sym2ltspice.ulp, and was

obtained from the LTSpice users' YahooGroup at:

http://f1.grp.yahoofs.com/v1/8FrvTKqgkDAmQ4F6EgbLwMU__aSS5qrxUjLGMbsfuxV7Wp3LI_T9EF2y18tr98kKGfOVKkQeST9-2iJ0gliUsrEzxxc3t34/%20Util/sym2ltspice.zip

 

The usage info that comes up in Eagle's control panel is:

"Export a symbol to a LTspice/SwitcherCAD III symbol

Usage: RUN sym2ltspice symbolname

The LTspice symbol file is saved in the project directory, if no file name

is specified.

The created symbol lacks some attributes, therefore it must be edited with

the LTspice symbol editor afterwards."

 

I can't get this ULP to find the actual "symbol." Every time

sym2ltspice.ulp runs it generates this error message:  "File not found.

Check the filename and try again."

 

Even though Eagle shows the symbol as having a file extension, the symbol

itself does not actually have an absolute folder location, because it is

embedded within the library file. Inserting the symbol's name into the

"symbolname" parameter produced the error message. I tried using the

absolute directory location of the libray, instead of the symbol name -- as

well as both. I also supplied an exact location for the LTSpice file to be

written. But nothing worked. Adding the .sym file extension to the symbol

name didn't work either.

 

I'm running the ULP within Eagle's library editor. The symbol I'm trying to

export to LTSpice is loaded into the editor's window. Then I go to "run"

and select sym2ltspice.ulp, typing in the necessary parameters. The ULP

always fails to find the symbol when using the parameters I have supplied.

I've tried everything reasonable, and also searched the net for other users

of this ULP, but have come up empty-handed.

 

Any hints as to what might work would be greatly appreciated.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

 

  • Sign in to reply
  • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube