Charlie Edmondson - Orcad bus names using leading 0's

[rickman]

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

 

[Charlie Edmondson]

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus names.

Charlie

 

[rickman]

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.

 

[Genome]

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.

Why not write BUS[15:100] BUS[15:101]......

DNA

 

[rickman]

rickman wrote:

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.

Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.

 

[Genome]

Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so that
signal
names sort correctly. That means I would name a bus BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I
am
getting errors in Orcad about wires with only one connection. Is
this
the reason? I don't see anything in the help that says I can or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.

Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.

I would recommend that you ignore me as someone who doesn't know what you
are really doing so I naturally don't know what I'm talking about. However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that is not
a leading zero.

Now I get the impression that things are more complicated than that and if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact you
haven't used them all in the design.

On the other hand if it doesn't then you can have...

BUS15:100
BUS15:101
BUS15:102

And so on. Then things will still sort correctly and if you (I) am lucky
when it does whatever it does it will ignore the ones you haven't referenced
and still come up with the right answer.

DNA

 

[Keith]

Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so that
signal
names sort correctly. That means I would name a bus BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I
am
getting errors in Orcad about wires with only one connection. Is
this
the reason? I don't see anything in the help that says I can or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.


Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.

I would recommend that you ignore me as someone who doesn't know what you
are really doing so I naturally don't know what I'm talking about. However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that is not
a leading zero.

Now I get the impression that things are more complicated than that and if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact you
haven't used them all in the design.

I think you misunderstand. BUS[15:100] would be a bundle of
BUS[15], BUS[16], BUS[17],...,BUS[100], which is 86 wires. I think
your idea is sound and perhaps should be something more like:
BUS[100:115], which would be sixteen wires and sort correctly.

 

[Genome]

Genome wrote:
Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so that
signal
names sort correctly. That means I would name a bus BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01...
I
am
getting errors in Orcad about wires with only one connection. Is
this
the reason? I don't see anything in the help that says I can or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.


Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.

I would recommend that you ignore me as someone who doesn't know what you
are really doing so I naturally don't know what I'm talking about.
However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that is
not
a leading zero.

Now I get the impression that things are more complicated than that and
if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact you
haven't used them all in the design.

I think you misunderstand. BUS[15:100] would be a bundle of
BUS[15], BUS[16], BUS[17],...,BUS[100], which is 86 wires. I think
your idea is sound and perhaps should be something more like:
BUS[100:115], which would be sixteen wires and sort correctly.

So BUS[100:115] defines BUS[100] to BUS[115]

I guessed that BUS was a BUS and it might be named as BUS[1] to identify it
as a different BUS from BUS[2] and then within each BUS there would be WIRES
such that BUS[1:1] would be WIRE number 1 in BUS number 1 and BUS[2:1] would
be WIRE number 1 in BUS number 2.

It's not a case of misunderstanding..... I just don't have a clue. However,
if there is a solution that results this is good. Have you ever tried to
download RAR files when the poster didn't include the extra zeroes to make
things sort correctly? No! forget that analogy.

DNA

 

[Keith]

Genome wrote:
Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so that
signal
names sort correctly. That means I would name a bus BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01...
I
am
getting errors in Orcad about wires with only one connection. Is
this
the reason? I don't see anything in the help that says I can or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.


Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.


I would recommend that you ignore me as someone who doesn't know what you
are really doing so I naturally don't know what I'm talking about.
However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that is
not
a leading zero.

Now I get the impression that things are more complicated than that and
if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact you
haven't used them all in the design.

I think you misunderstand. BUS[15:100] would be a bundle of
BUS[15], BUS[16], BUS[17],...,BUS[100], which is 86 wires. I think
your idea is sound and perhaps should be something more like:
BUS[100:115], which would be sixteen wires and sort correctly.

So BUS[100:115] defines BUS[100] to BUS[115]

Correct, in VHDL speak "SIGNAL bus: std_logic_vector(100 to 115)"

I guessed that BUS was a BUS and it might be named as BUS[1] to identify it
as a different BUS from BUS[2] and then within each BUS there would be WIRES
such that BUS[1:1] would be WIRE number 1 in BUS number 1 and BUS[2:1] would
be WIRE number 1 in BUS number 2.

It's not a case of misunderstanding..... I just don't have a clue. However,
if there is a solution that results this is good. Have you ever tried to
download RAR files when the poster didn't include the extra zeroes to make
things sort correctly? No! forget that analogy.

Never figured out what RAR files were good for.

 

[Genome]

Genome wrote:
Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so
that
signal
names sort correctly. That means I would name a bus
BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00,
BUS01...
I
am
getting errors in Orcad about wires with only one connection.
Is
this
the reason? I don't see anything in the help that says I can
or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in
bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will
sort
correctly in any text format like in a spreadsheet or even a
simple
entry in a Word document. So I guess I will still have to sort
the
docs by hand.


Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86
signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.


I would recommend that you ignore me as someone who doesn't know what
you
are really doing so I naturally don't know what I'm talking about.
However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that
is
not
a leading zero.

Now I get the impression that things are more complicated than that
and
if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact
you
haven't used them all in the design.

I think you misunderstand. BUS[15:100] would be a bundle of
BUS[15], BUS[16], BUS[17],...,BUS[100], which is 86 wires. I think
your idea is sound and perhaps should be something more like:
BUS[100:115], which would be sixteen wires and sort correctly.

So BUS[100:115] defines BUS[100] to BUS[115]

Correct, in VHDL speak "SIGNAL bus: std_logic_vector(100 to 115)"

I guessed that BUS was a BUS and it might be named as BUS[1] to identify
it
as a different BUS from BUS[2] and then within each BUS there would be
WIRES
such that BUS[1:1] would be WIRE number 1 in BUS number 1 and BUS[2:1]
would
be WIRE number 1 in BUS number 2.

It's not a case of misunderstanding..... I just don't have a clue.
However,
if there is a solution that results this is good. Have you ever tried to
download RAR files when the poster didn't include the extra zeroes to
make
things sort correctly? No! forget that analogy.

Never figured out what RAR files were good for.

Sometimes you are forced to comply with other peoples concepts of standards.

DNA

 

[Spehro Pefhany]

Genome wrote:
Charlie Edmondson wrote:
rickman wrote:

I am accustomed to using two digits in my bus numbering so that
signal
names sort correctly. That means I would name a bus BUS[15:00]
instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01...
I
am
getting errors in Orcad about wires with only one connection. Is
this
the reason? I don't see anything in the help that says I can or
can't
do this.

Jim Thompson suggested I put your name in the subject line...

Ok, double checked. Capture does not support leading zeros in bus
names.

Charlie

Ok, thanks. I guess I am remembering what I used to do in VHDL.

I like to use double digits so that all the signal names will sort
correctly in any text format like in a spreadsheet or even a simple
entry in a Word document. So I guess I will still have to sort the
docs by hand.


Why not write BUS[15:100] BUS[15:101]......

I'm not sure what you are saying. 15:100 would be a bus of 86 signals!
I am trying to create a bus of N signals with names of BUS00, BUS01,
BUS02... BUSnn

But you can't do that in Orcad. So I guess I won't.


I would recommend that you ignore me as someone who doesn't know what you
are really doing so I naturally don't know what I'm talking about.
However,
pretending to be smart, I thought.....

If the software will not accept a leading zero give it something that is
not
a leading zero.

Now I get the impression that things are more complicated than that and
if
you define BUS15:100 (I don't do hex but I believe your 86) then the
software immediatly generates an 86 line bus and moans about the fact you
haven't used them all in the design.

I think you misunderstand. BUS[15:100] would be a bundle of
BUS[15], BUS[16], BUS[17],...,BUS[100], which is 86 wires. I think
your idea is sound and perhaps should be something more like:
BUS[100:115], which would be sixteen wires and sort correctly.

So BUS[100:115] defines BUS[100] to BUS[115]

Correct, in VHDL speak "SIGNAL bus: std_logic_vector(100 to 115)"

I guessed that BUS was a BUS and it might be named as BUS[1] to identify it
as a different BUS from BUS[2] and then within each BUS there would be WIRES
such that BUS[1:1] would be WIRE number 1 in BUS number 1 and BUS[2:1] would
be WIRE number 1 in BUS number 2.

It's not a case of misunderstanding..... I just don't have a clue. However,
if there is a solution that results this is good. Have you ever tried to
download RAR files when the poster didn't include the extra zeroes to make
things sort correctly? No! forget that analogy.

Never figured out what RAR files were good for.

They're for R.. ARRRRRRR piracy.


Best regards,
Spehro Pefhany

 

[Peter]

I am accustomed to using two digits in my bus numbering so that signal
names sort correctly. That means I would name a bus BUS[15:00] instead
of BUS[15:0] so that the lower signals would be BUS00, BUS01... I am
getting errors in Orcad about wires with only one connection. Is this
the reason? I don't see anything in the help that says I can or can't
do this.

Jim Thompson suggested I put your name in the subject line...

I am still on SDT/386 and love it 1994 vintage.

With Protel PCB 2.8, c. 1995.

It does all I need.


Peter.