Edit the VALUE of parts on a schematic diagram

[Anonymous]

So I've moved to Linux and decided that Eagle is by far the best EDA package and has the best library support, which incidental works great, if not better than on Windows.

I've also checked out the FAQ, which has a VALUE reference in the context of layout (PCB), but does not mention it in the context of the Schematic Diagram. So I have an almost embarrassingly basic question.

The question is simply how and where do you edit the parts/symbols in the schematic diagram to allow the display of the basic value of components, that have been added from the libraries, as the value fields appear to be fixed.

ie.  to display      C1     10nF,    R1    1K      etc.

NOT

     C1     08055C103K4Z4A

Thank You

[jjm17XBGQ]

Name and Values are on dedicated layers. 

The DISP  command controls the layer visibility.

[Anonymous]

Thank you, that's allowed me to remove the visibility of the value, as defined in the library part. ie. it's got rid of  the long entries such as 08055C103K4Z4A.

Now what is the correct way to add a short visible value for the parts, particularly the C, R and L's, ie. 10nF.

[one-of-the-robs]

That's mostly a question of house style. Eagle will render the "value" from the value assigned to a part. If the library is designed with user-values enabled (which most of them are, or at least used to be) then you can change that for individual parts with the VALUE tool. The value is a generic text field - you can type anything you like in there. What you type depends on your house style. Some people like to have full manufacturer part number in there. Others prefer just a generic ("10uF 16V" or similar). Eagle isn't fussed either way, except...

I think the managed libraries tend to be specifically named by part number because the STEP file for the 3D image is specific to a certain part. So the quick and easy way is not to use the managed libraries.

[Anonymous · Accepted solution]

Thank you, that's all very helpful.

The "used to be" explains why this was never an issue when I was using 8.something for quite a while on Windows, or maybe I was just lucky.

For the time being I've created Layer 101 SortValues, so at least the Schematic can be made to looks right. Point taken about not altering data in instances of the managed library parts. I'll have to get back into creating my own library parts.

Thanks again.

[jjm17XBGQ]

Imo this will produce more "side effects" then solutions. E.g. the BOM export did not work with parts on layer 1xx.

Better use the standard way. If you need different part naming, do it in names and create an attribute with the original name. The BOM handles the attributes and you can move them to a layer, make them visible or not. More important imo is the consistent procedure with the rest of the world.