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 Chat (English) Delete individual signals
  • 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 2 replies
  • Subscribers 178 subscribers
  • Views 891 views
  • Users 0 members are here
Related

Delete individual signals

Former Member
Former Member over 14 years ago

Greetings,

 

I'm trying to use Eagle's scripting commands to delete a particular signal present on the board.  Typing "delete signals" will delete all signals, but I just want to delete one signal by its name, using script commands only.  (I don't want to undo any more routing than necessary by issuing a command to delete signals, and consequently have to add them all back again and start over in the routing process.)  It appears the delete command wants an element name as its argument, and not a signal name.  I can delete a particular airwire using the delete command if I give it a coordinate of the airwire as its argument, however I cannot know this coordinate information outside of the board where I'm generating the script, so this way won't work for me.

 

I am using the layout editor only (no forward/back-annotation with a schematic).  The reason why we are not using the schematic editor is because we are developing a new PCB hardware description language called PHDL (similar to VHDL) that describes PCB schematics in pure text, therefore there is no need for the schematic capture side of the tools.  It is our hope that hierarchical PCB IP can be generated and "instanced" in new PCB designs, alleviating the bottleneck inherent with re-inventing a new PCB from scratch every time.

 

With that, does anyone know if the delete command supports deleting entire signals from within the layout editor, and what its syntax is?

  • Sign in to reply
  • Cancel
  • Former Member
    Former Member over 14 years ago

    Brad R wrote:

     

    With that, does anyone know if the delete command supports deleting

    entire signals from within the layout editor, and what its syntax is?

     

    As I understand it, this cannot be done,  I'm prepared to be corrected

    though.

     

    An option is a small ULP which you call from your script that finds the

    coords and deletes the signal at that time.

    If the signal is routed,first ripup the signal by name and then find the

    coords of the remaining airwire/airwires and delete them.

     

    HTH

    Warren

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago

    On 8/15/2011 6:22 PM, Brad R wrote:

    Greetings,

     

    I'm trying to use Eagle's scripting commands to delete a particular signal present on the board.  Typing "delete signals" will delete all signals, but I just want to delete one signal by its name, using script commands only.  (I don't want to undo any more routing than necessary by issuing a command to delete signals, and consequently have to add them all back again and start over in the routing process.)  It appears the delete command wants an element name as its argument, and not a signal name.  I can delete a particular airwire using the delete command if I give it a coordinate of the airwire as its argument, however I cannot know this coordinate information outside of the board where I'm generating the script, so this way won't work for me.

     

    I am using the layout editor only (no forward/back-annotation with a schematic).  The reason why we are not using the schematic editor is because we are developing a new PCB hardware description language called PHDL (similar to VHDL) that describes PCB schematics in pure text, therefore there is no need for the schematic capture side of the tools.  It is our hope that hierarchical PCB IP can be generated and "instanced" in new PCB designs, alleviating the bottleneck inherent with re-inventing a new PCB from scratch every time.

     

    With that, does anyone know if the delete command supports deleting entire signals from within the layout editor, and what its syntax is?

     

     

    Hi Brad,

     

    I believe Warren's description is correct. I just wanted to add that

    with the next release of EAGLE our file format will be XML and

    completely text-based. So the capabilities you are seeking to create

    with PHDL will become available.

     

    hth,

     

    Jorge Garcia.

     

    • Cancel
    • Vote Up 0 Vote Down
    • 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 © 2026 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