G$1 next to reference designator, how to get rid of this?

Zoran wrote:

Try changing a power symbol and no-connect symbol add level to 'request'

and leave the inverter at 'next'. When adding the part to the schematic,

only the inverter gate will be added and you will have to invoke the

other two if you want them placed.

 

'G$#' is an automatic gate name that Eagle sets when adding a symbol to

a device, where # is the gate number. When having multiple 'next' or

'can' gates of the same device in a schematic, a gate name is appended

to the part name, that's why you are getting 'U6G$1'.

 

Thank you, Zoran, that did the trick! Strange thing is, I've looked in

other libraries for clues and there are cases where it's the same, main

symbol with "next" and the power with "can", and it works. But, main

thing is, the G$1 is gone.

You might also want to rename the gate from an automatic 'G$1' to

something more meaningful, e.g. '-#'; that way you would have something

like that when adding several 'next' or 'can' gates from one device:

'U6-1', 'U6-2', 'U6-3', and so on.

 

Usually with multipart symbols I use A, B, C, and so on.

I hope this helps.

 

It sure did

--

Regards, Joerg

http://www.analogconsultants.com/

Strange thing is, I've looked in

other libraries for clues and there are cases where it's the same, main

symbol with "next" and the power with "can", and it works.

That's strange because 'next' and 'can' are essentially the same except

for the fact that 'next' is added automatically with ADD command and

'can' can only be added with INVOKE. Gate numbers should be there. Or

maybe I must brush up on this a little

But, main thing is, the G$1 is gone.

Good Just remember to invoke and connect the power pins if they are

not already implicitly connected to the supply.

Zoran

Strange thing is, I've looked in

other libraries for clues and there are cases where it's the same, main

symbol with "next" and the power with "can", and it works.

That's strange because 'next' and 'can' are essentially the same except

for the fact that 'next' is added automatically with ADD command and

'can' can only be added with INVOKE. Gate numbers should be there. Or

maybe I must brush up on this a little

But, main thing is, the G$1 is gone.

Good Just remember to invoke and connect the power pins if they are

not already implicitly connected to the supply.

Zoran

Zoran wrote:

>> Strange thing is, I've looked in

>> other libraries for clues and there are cases where it's the same, main

>> symbol with "next" and the power with "can", and it works.

 

That's strange because 'next' and 'can' are essentially the same except

for the fact that 'next' is added automatically with ADD command and

'can' can only be added with INVOKE. Gate numbers should be there. Or

maybe I must brush up on this a little

 

>> But, main thing is, the G$1 is gone.

 

Good Just remember to invoke and connect the power pins if they are

not already implicitly connected to the supply.

 

Since I do analog stuff I have to almost always invoke the power pins.

But there Eagle has a bug, at least 4.16 does: When you invoke power

pins they show up with the refdes U6P (or U6G$2 if nothing was edited).

Very ugly when you scoot it over the device symbol. You can smash, move

and delete but this does not "stick", then the U6P pops right back up.

Entering a blank for the power pins in the library editor doesn't work,

it requires that something is entered.

--

Regards, Joerg

http://www.analogconsultants.com/

Joerg wrote:

Zoran wrote:

>>> Strange thing is, I've looked in

>>> other libraries for clues and there are cases where it's the same,

>>> main symbol with "next" and the power with "can", and it works.

>>

>> That's strange because 'next' and 'can' are essentially the same

>> except for the fact that 'next' is added automatically with ADD

>> command and 'can' can only be added with INVOKE. Gate numbers should

>> be there. Or maybe I must brush up on this a little

>>

>>> But, main thing is, the G$1 is gone.

>>

>> Good Just remember to invoke and connect the power pins if they

>> are not already implicitly connected to the supply.

>>

>

Since I do analog stuff I have to almost always invoke the power pins.

But there Eagle has a bug, at least 4.16 does: When you invoke power

pins they show up with the refdes U6P (or U6G$2 if nothing was

edited). Very ugly when you scoot it over the device symbol. You can

smash, move and delete but this does not "stick", then the U6P pops

right back up. Entering a blank for the power pins in the library

editor doesn't work, it requires that something is entered.

 

--

Regards, Joerg

 

http://www.analogconsultants.com/

Your answer may lay in a similar question I asked in this post.

http://www.eaglecentral.ca/forums/index.php/m/131169/c6b26c5fc772ccae538bde44e40f0b15/#page_top

Or search for the topic in eagle.suggest.eng

Enhancement to ADDLEVEL to prevent gate name being appended

It would be good to have the ability to prevent the gate name being

appended

to the gate, and thus reduce schematic clutter.

...

Klaus replied

Just use the ">PART" placeholder in your symbol instead of ">NAME".

HTH

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

But there Eagle has a bug, at least 4.16 does: When you invoke power

pins they show up with the refdes U6P (or U6G$2 if nothing was edited).

Power pins that are part of a device are also symbols like any other

gate. If a symbol contains a text variable e.g. >NAME or >VALUE, it will

be displayed in the schematic. So if you don't want these texts

displayed, you have 2 options:

- smash each part in the schematic and delete the texts, or...

- remove the texts in the symbol if you don't need them anywhere at all.

Name and value will get back if you unsmash (shift+smash) the part.

That's how it works in 6.2, I can't tell for the 4.16, that was some

time ago...

The only thing you can't smash is a pin / pad name, but you can choose

to display the pin name, the pad name, both, or none (off).

Entering a blank for the power pins in the library editor doesn't work,

it requires that something is entered.

Each gate must have a name, just the same as any part in the schematic /

board, and spaces are not allowed.

You however don't have to display these names with >NAME text variable

if you don't want to.

Just use the ">PART" placeholder in your symbol instead of ">NAME".

This one I didn't know. Thanks!

@Joerg:

Just check Help->Editor Commands->TEXT where variables are explained.

Zoran

Zoran wrote:

>> Just use the ">PART" placeholder in your symbol instead of ">NAME".

 

This one I didn't know. Thanks!

 

@Joerg:

Just check Help->Editor Commands->TEXT where variables are explained.

 

Also search for >PART in the pdf Manual (found in the DOCS folder) where

examples of the use of  >PART and >GATE are shown.

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Zoran wrote:

>> But there Eagle has a bug, at least 4.16 does: When you invoke power

>> pins they show up with the refdes U6P (or U6G$2 if nothing was edited).

 

Power pins that are part of a device are also symbols like any other

gate. If a symbol contains a text variable e.g. >NAME or >VALUE, it will

be displayed in the schematic. So if you don't want these texts

displayed, you have 2 options:

- smash each part in the schematic and delete the texts, or...

This does not work in 4.16. After a refresh it pops back up.

- remove the texts in the symbol if you don't need them anywhere at all.

 

Thanks, that finally did the trick. Calling it >PART made the dreaded

G$1 re-appear, not so good. Having a different symbol with nothing in

there is much better.

Name and value will get back if you unsmash (shift+smash) the part.

It even does without unsmashing in 4.16.

That's how it works in 6.2, I can't tell for the 4.16, that was some

time ago...

 

The only thing you can't smash is a pin / pad name, but you can choose

to display the pin name, the pad name, both, or none (off).

 

>> Entering a blank for the power pins in the library editor doesn't work,

>> it requires that something is entered.

 

Each gate must have a name, just the same as any part in the schematic /

board, and spaces are not allowed.

You however don't have to display these names with >NAME text variable

if you don't want to.

 

Well, I just deleted it in the symbol via the library editor -> gone ->

no more G$1 stuff -> problem fixed

Thanks, Zoran.

--

Regards, Joerg

http://www.analogconsultants.com/

Warren Brayshaw wrote:

Joerg wrote:

>> Zoran wrote:

>>>> Strange thing is, I've looked in

>>>> other libraries for clues and there are cases where it's the same,

>>>> main symbol with "next" and the power with "can", and it works.

>>> That's strange because 'next' and 'can' are essentially the same

>>> except for the fact that 'next' is added automatically with ADD

>>> command and 'can' can only be added with INVOKE. Gate numbers should

>>> be there. Or maybe I must brush up on this a little

>>>

>>>> But, main thing is, the G$1 is gone.

>>> Good Just remember to invoke and connect the power pins if they

>>> are not already implicitly connected to the supply.

>>>

>> Since I do analog stuff I have to almost always invoke the power pins.

>> But there Eagle has a bug, at least 4.16 does: When you invoke power

>> pins they show up with the refdes U6P (or U6G$2 if nothing was

>> edited). Very ugly when you scoot it over the device symbol. You can

>> smash, move and delete but this does not "stick", then the U6P pops

>> right back up. Entering a blank for the power pins in the library

>> editor doesn't work, it requires that something is entered.

>>

>> --

>> Regards, Joerg

>>

>> http://www.analogconsultants.com/

 

Your answer may lay in a similar question I asked in this post.

http://www.eaglecentral.ca/forums/index.php/m/131169/c6b26c5fc772ccae538bde44e40f0b15/#page_top

Or search for the topic in eagle.suggest.eng

Enhancement to ADDLEVEL to prevent gate name being appended

 

>> It would be good to have the ability to prevent the gate name being

appended

>> to the gate, and thus reduce schematic clutter.

>> ...

 

Klaus replied

Just use the ">PART" placeholder in your symbol instead of ">NAME".

 

That didn't work, it made it pop back. But Zoran's hint was dead on:

Deleting it in the library editor makes it go away for good. The only

downside is that the text in that one part now has a different and

somewhat ugly font, but, oh well.

--

Regards, Joerg

http://www.analogconsultants.com/

The only

downside is that the text in that one part now has a different and

somewhat ugly font

I don't know what's your definition of ugly but you can try changing the

font in your symbol with ->change ->font ->vector/proportional/fixed.

Pick the one you consider least ugly That will work unless you have

set your environment to always show vector font.

It would be nice if we could just choose a (true type) font to our

liking but that's another story...

Thanks, Zoran.

You're welcome. Glad I could help.

Zoran

Zoran wrote:

>> The only

>> downside is that the text in that one part now has a different and

>> somewhat ugly font

 

I don't know what's your definition of ugly but you can try changing the

font in your symbol with ->change ->font ->vector/proportional/fixed.

Pick the one you consider least ugly That will work unless you have

set your environment to always show vector font.

 

It would be nice if we could just choose a (true type) font to our

liking but that's another story...

 

>> Thanks, Zoran.

 

You're welcome. Glad I could help.

 

The renumbering scheme still groans about "Parts on the same coordinate"

and then aborts. So I have to move the supply pins to lalaland, do the

renumbering, and then move them back. But I guess that falls under minor

inconveniences. It's like driving old trucks where you have to

double-clutch when down-shifting, and none of us complained

--

Regards, Joerg

http://www.analogconsultants.com/