Creating external components

Anonymous

Creating external components

Anonymous
Not applicable

Greetings all,

I am trying to create some simple external components in the library manager. (Section 8.8 of the documentation)

This will be used for chassis mounted pots, switches, etc.

These devices need to appear on the schematic but not on the circuit board layout.

I've really been struggling with this because it seems the documentation in Section 8 does not match the software. The procedures and icons in the documentation are either not there or don't match.

I want to make a simple SPST switch. I first create the new library and save it as "External Devices."

After that I just don't know what to do. I can "Add Device" but there's nothing there. I can "Import" but I'm not sure if that's the right way to do it.

Can someone give me a quick step by step workflow for this?

Thanks.

Mitch

0 Likes
Reply
927 Views
3 Replies
Replies (3)

Yura.Ivanov.VLuki
Collaborator
Collaborator

In your previous topic, I posted an example where the transformer and potentiometer are in the electrical circuit, but outside the board. Everything is done as in the manual.

Good luck!

 Placing a component off board 

0 Likes

Anonymous
Not applicable

Thank you for your reply again. Yes, I understand what you are saying. However, you are using version 7.x of Eagle.

I'm using version 9.5.2. The documentation in the manual doesn't match my version of Eagle.

My solution is to "import" existing devices, delete the package and footprint, then add the _EXTERNAL_ attribute.

This is not in the manual and I don't know if this is the correct way to do it.

library-Capture.JPGlibrary-Capture2.JPG

 

 

 

 

 

 

 

The symbol editor is also very different and again not covered in the manual.

What I'm asking is, when can we expect the manual to catch up with the latest version?

Thanks for the help.

0 Likes

Yura.Ivanov.VLuki
Collaborator
Collaborator

@Anonymous  написал (-а): The symbol editor is also very different and again not covered in the manual.

What I'm asking is, when can we expect the manual to catch up with the latest version?


There must be a lack of professionals. Uncle Bob the ioc would help.

The Clean Coder: A Code of Conduct for Professional Programmers 

0 Likes