Formatting Xref net labels

Hi,

On 11/19/12 22:49, Vidar (Z) wrote:

Hi

 

Normally I have used only the text-based net labels on line that goes

from one sheet to another. My wish is to use the XREF option but I am

not comfortable with the format options.

 

My "big" problem is that the signal name for a given net label comes

inside the flag. I would prefer all symbols to be of equal size and to

have the text align on beside of the net flag instead.

 

not like this            but like this

  ______________________          _____

/NETLABEL_SIGNAL_NAME |       /     | NETLABEL_SIGNAL_NAME

\______________________|        \_____|

 

If not existing as an option already I would recommend to make the order

of the label xref formatting tags relevant (as set in misc menu) to the

result. Se my examples below:

 

                 ________________

%F%N (%S)      / NETLABEL (1)  |

                \________________|

 

                 _____

%N %F(%S)      / (1) | NETLABEL

                \_____|

                 _____

%N (%S)%F      /     | NETLABEL (1)

                \_____|

 

Here everything coming in front of the %F tag ends up outside the flag

and everything after %F ends up inside. The flag symbol would thus have

a minimum size like say 3 letters.

 

Second. Is it possible to have flags indicating direction of a net? I.e.

if signal is in, out or bidirectional. This should be possible to change

with a change command like for example CHANGE DIRECTION or CHANGE FLAG

if not existing as an option already somewhere.

 

input             bi              output

  _______          ______         ______

_/       |       /      \       |      \

\_______|        \______/       |______/

 

Thanks, but some questions on this:

- What flags would you set if the net has many (>2) pin connections ?

- How should it behave is a user has a net with unlogical connections, say input - input ?

This can cause confusion.

Regards,

Walter Spermann

 

NOTE: I asked this as an question in the support forum, but as mentioned

there I would put it here as a suggestion if it was not possible in some

other way already. As far as I can see, it is not, though I am using

glasses....!*

 

Breg

Vidar (Z)

--

-

Walter Spermann

Softwareentwicklung

CadSoft Computer GmbH

Pleidolfweg 15

84568 Pleiskirchen

Tel.: 08635/6989-10

www.cadsoft.de

-

Registergericht: Amtsgericht Traunstein HRB 5573

Geschäftsführer: Thomas Liratsch

-

On 20. nov. 2012 18:22, Walter Spermann wrote:

Hi,

 

On 11/19/12 22:49, Vidar (Z) wrote:

>> Hi

>>

>> Normally I have used only the text-based net labels on line that goes

>>..cut due to length, see original post

>> input             bi              output

>>    _______          ______         ______

>> _/       |       /      \       |      \

>>   \_______|        \______/       |______/

>>

Thanks, but some questions on this:

  - What flags would you set if the net has many (>2) pin connections ?

  - How should it behave is a user has a net with unlogical connections, say input - input ?

This can cause confusion.

 

Regards,

Walter Spermann

 

>>

>> NOTE: I asked this as an question in the support forum, but as mentioned

>> there I would put it here as a suggestion if it was not possible in some

>> other way already. As far as I can see, it is not, though I am using

>> glasses....!*

>>

>> Breg

>> Vidar (Z)

>

There is a lot of things that can cause confusions, but the design will

never be better than the effort the user puts into it. And if a users

connects two inputs, or worse two outputs, that’s the users problem and

an ERC will show this. And most professional eCAD software’s has this

option already successfully implemented and I see no reason for why

Eagle should not.

I guess that, to meet the problem you rise, initially the direction

should be set to the direction of the closest pin. In most cases this

will reflect the users intention. When using the change direction/flag

option you can then force the symbol to reflect whatever direction you

want.

The motivation to have this functionality is not to show the given

direction on the device pins, which can be wrong because of a faulty

library device or wrong usage, but the direction as seen from the users

perspective and planned function. We are in other words talking about a

way of labeling nets to tell their names and signals flow-direction

In fact. If you try to add a label flag to a net and you expect to see

an "out" symbol and sees an "in" symbol instead, you should start thinking.

NOTE: I just noticed an embarrassing error i did in my ASCII drawings

for the output symbol. I guess everybody understood what I meant, but

here is the correct drawing.

   input             bi              output

     _______          ______         ______

   _/       |       _/      \      _|      \

    \_______|        \______/       |______/

the "tail" where the net is connected should off-course be on the

opposite position of where the arrow is on the output symbol.

Breg

Vidar (Z)

On 20. nov. 2012 18:22, Walter Spermann wrote:

Hi,

 

On 11/19/12 22:49, Vidar (Z) wrote:

>> Hi

>>

>> Normally I have used only the text-based net labels on line that goes

>>..cut due to length, see original post

>> input             bi              output

>>    _______          ______         ______

>> _/       |       /      \       |      \

>>   \_______|        \______/       |______/

>>

Thanks, but some questions on this:

  - What flags would you set if the net has many (>2) pin connections ?

  - How should it behave is a user has a net with unlogical connections, say input - input ?

This can cause confusion.

 

Regards,

Walter Spermann

 

>>

>> NOTE: I asked this as an question in the support forum, but as mentioned

>> there I would put it here as a suggestion if it was not possible in some

>> other way already. As far as I can see, it is not, though I am using

>> glasses....!*

>>

>> Breg

>> Vidar (Z)

>

There is a lot of things that can cause confusions, but the design will

never be better than the effort the user puts into it. And if a users

connects two inputs, or worse two outputs, that’s the users problem and

an ERC will show this. And most professional eCAD software’s has this

option already successfully implemented and I see no reason for why

Eagle should not.

I guess that, to meet the problem you rise, initially the direction

should be set to the direction of the closest pin. In most cases this

will reflect the users intention. When using the change direction/flag

option you can then force the symbol to reflect whatever direction you

want.

The motivation to have this functionality is not to show the given

direction on the device pins, which can be wrong because of a faulty

library device or wrong usage, but the direction as seen from the users

perspective and planned function. We are in other words talking about a

way of labeling nets to tell their names and signals flow-direction

In fact. If you try to add a label flag to a net and you expect to see

an "out" symbol and sees an "in" symbol instead, you should start thinking.

NOTE: I just noticed an embarrassing error i did in my ASCII drawings

for the output symbol. I guess everybody understood what I meant, but

here is the correct drawing.

   input             bi              output

     _______          ______         ______

   _/       |       _/      \      _|      \

    \_______|        \______/       |______/

the "tail" where the net is connected should off-course be on the

opposite position of where the arrow is on the output symbol.

Breg

Vidar (Z)