It probably makes more sense for the serial interface to just be a 6 pin bus?

[mithro]

Not sure... but that way the top sheet would just have a wire per serial port....

[ayushsagar]

I thought about that, but it wouldn't look neat. The post-fixed numbers in signal lines should help us to differentiate.

[mithro]

It would make changing the number of pins much easier / quicker too.

Again, please don't close an issue until you can confirm the issue is resolved (IE we come to an agreement that your solution is best or that we need to change it).

[ayushsagar]

I'm not quite sure how buses would make changing the number of pins easier. Because afaik from the documentation, I have to make these labels for each pin any way, and these buses seem to behave nothing more than a thick line?

[mithro]

Because the layout of the top page is easier. You don't have to push multiple pins around. (It should also be "select all busses" and then change number of lines parameter.

[ayushsagar]

You don't have to push multiple pins around.

Pins will have to be multiple in any case. e.g. http://packi.ch/data/news/attachments/entry/50/mem_sch1.png

"select all busses" and then change number of lines parameter.

I'm not sure what this means, can you explain in more detail or with an example?

The only difference that I can see is it will make the blocks connected to anyone who's not used to seeing label connections. But then we would have to be consistent and use this scheme throughout schematic and that would add more effort for making connections between blocks every time.

We can still enumerate and add labels using the Insert key to conveniently add connection labels. The bus only seems to be a visual guide for showing where a group of related signals are going.

[ayushsagar]

P.S. By enumeration I mean adding label with names like A0, A1, A2 in series gets automated by pressing Ins key. We can probably use that instead of RX0, TX0 etc, but using names like RX, TX also tells me about the direction of signals, so I'm not sure if using a series like A0, A1, A2 ... is a good idea.

[ayushsagar]

This was the closest I could do from what I understand: https://www.dropbox.com/s/393woj5762i6yyr/Printing%20Print%20Schematic_Page_1.png in the commit https://github.com/ayushsagar/HDMI2USB-vmodserial/commit/34c8ab63638a96ae1f2e24fba49026d6ee372543

I don't think we can combine 6 pins on a sheet to form a bus/array type pin corresponding to a port.

[mithro]

Here are some screenshots of what I was trying to get you to do.

At the top level you have busses, the hierarchical pins are bus pins rather than individual pins. In the lower sheets you can break them out into the individual pins.

[mithro]

Example at; http://radiationlaboratories.blogspot.com.au/2011/08/kicad-how-to-use-bus-with-hierarchical.html

[ayushsagar]

Hi, I tried this today but I got DRC errors that suggest that we need to expand the bus to make the connections.

Take a look at bus to bus connections in top sheet

Bus expanded

See the ERC errors below

[mithro]

Firstly you have a number of problems unrelated to these busses. Power pins (VCC, etc) are of type "passive" not input/output.

Next you have multiple problems with this bus make up;

• I was suggesting a bus per slot (see my picture).
• Bus pins need to be named - IE For pin 1 of bus SLOT1, the net name should be SLOT11.
• Your not using junctions to connect two nets of the different names.

[ayushsagar]

Bus per slot didnt work i tried On 27-Jun-2014 8:45 am, "Tim Ansell" notifications@github.com wrote:

Firstly you have a number of problems unrelated to these busses. Power pins (VCC, etc) are of type "passive" not input/output.

Next you have multiple problems with this bus make up;

• I was suggesting a bus per slot (see my picture).
• Bus pins need to be named - IE For pin 1 of bus SLOT1, the net name should be SLOT11.
• Your not using junctions to connect two nets of the different names.

— Reply to this email directly or view it on GitHub https://github.com/ayushsagar/HDMI2USB-vmodserial/issues/10#issuecomment-47304118 .

[mithro]

Why does a bus per slot not work? What did you actually try?

[ayushsagar]

Ok. I'll try the junctions part and let you know. On 27-Jun-2014 8:47 am, "Ayush Sagar" ayushsagar@gmail.com wrote:

Bus per slot didnt work i tried On 27-Jun-2014 8:45 am, "Tim Ansell" notifications@github.com wrote:

Firstly you have a number of problems unrelated to these busses. Power pins (VCC, etc) are of type "passive" not input/output.

Next you have multiple problems with this bus make up;

• I was suggesting a bus per slot (see my picture).
• Bus pins need to be named - IE For pin 1 of bus SLOT1, the net name should be SLOT11.
• Your not using junctions to connect two nets of the different names.

— Reply to this email directly or view it on GitHub https://github.com/ayushsagar/HDMI2USB-vmodserial/issues/10#issuecomment-47304118 .

[mithro]

With a single BUS pins need to be named 1->38, doing 1-6 multiple times is just the same set of pins, that is not what we want.

[mithro]

Your pictures don't match what is in the repository either; picture below.

[ayushsagar]

Still not working Try: https://github.com/ayushsagar/HDMI2USB-vmodserial/commit/e0792eb586bea6cecf3692d1285553a785cf0c54

[mithro]

This passes the DRC.