1) Equalisation of length of pairs of traces
From Board Design Resource Center
2) Delay (e.g. of clock for timing purposes)?
See also Adding delay intentionally
3) Reduce signal reflections due to discontinuities in trace width?
from Circuit Board Layout Techniques
See also How should I lay out timing matched traces?
The industry term for this is via in pad.
It's not a problem when you hand-solder components.
It can cause problems during automated SMT assembly. Solder, which was applied to the pad as a solder paste, can drain through the via and there will be an insufficient amount of solder to hold the part.
(Image came from this blog entry, which illustrates the ...
I think the placing of the parts is your biggest problem.
Look at U6 and the U13, U14, and U15.
U6 has multiple connections to U13, but those connections have to cross all the connections to U11 and U12 to get there.
U14 and U15 are similar - all the connections to them have to cross connections to other ICs to get to U6.
You've placed your parts in a ...
One very good reason, as I learned myself from a recent prototype, is reversing the physical layout of the IC in a circuit.
I plugged a through-hole version of this microcontroller into a socket backwards, and spent about an hour with an oscilloscope trying to determine why pins were not behaving as expected.
When I discovered the IC was in backwards (and ...
At I2C speeds, vias will cause you absolutely no problems at all.
At least, no problems in terms of track resistance, capacitance or inductance. However, if you have a 2 layer board, then using both layers is best done systematically, otherwise you can lead yourself into problems.
What many people do is to dedicate one layer of a board to ground. This ...
Manhattan routing is a PCB routing strategy. You use one dedicated layer for horizontal tracks and another layer for vertical tracks. No horizontal tracks are allowed on the vertical layer, and no vertical traces are used on the horizontal layer. This means that most connections will go trough a via, but this strategy can provide surprisingly dense boards ...
As an addition to Armandas' answer:
If you want to use vias, there is a simple trick to swap the lines: Rotate the vias by 90 degrees, i.e. put them "above" each other. If you enter both vias from the left in the top layer and leave them to the left in the bottom layer, both lines are swapped at no expense:
(Just a quick drawing as my schematics computer ...
Look at a map of Manhattan: streets are straight and at right angles. That's what you do on your PCB: horizontal and vertical lines.
There's also the concept of "Manhattan distance". That's the distance measured vertically, then horizontally, instead of a direct line.
There isn't one.
That said, there are some thing I've gathered over time. What you do with the ground planes depends heavily on what you're trying to do. You could be trying to provide low impedance paths, or you could be trying to isolate one area from another, or you could be trying to deal with EMI.
There certainly is a performance penalty for doing ...
There's nothing wrong with via in pad per say. As other people have noted an open via in pad can lead to soldering issues as the solder is sucked down the via hole. Hand soldering you'll be fine of course, also for small runs the manufacturer can just pre-fill the hole with solder by hand with an iron or a hot air pen. This usually eliminates most of the ...
why are they all not connected to each other on the top layer, since they are all the same net ?
Because this is a switching converter. In switching converters very high currents can flow, often these or only very short current pulses. If we "just" connect everything to the ground plane directly it is unclear where these currents actually flow. Yes all is ...
The 90º intersection will not be a issue for most traces. If your trace is very thin (< 15 mill) and/or the PCB boards aren't being professionally manufactured you can use mitered traces (chamfer) as helloworld922 pointed out. Adding chamfers will eliminate the 90º intersection and help to strengthen the trace. For high frequency traces (> 1GHz) it also ...
Your interpretation is overly simplistic. Real FPGAs have a complex hierarchy of routing resources, some for local connections only, some for medium-range connections and some for spanning the entire chip. These structures have been developed over many years of studying application designs, trying to strike a balance between the area required for routing ...
According to the help system of eagle, you can use the command
to ripup all polygons. You can limit this to polygons of a list of signals by
RIPUP @ GND VCC MYSIGNAL;
You can define a keyboard shortcut for RIPUP @; and another for RATSNEST; to simply toggle between filled and non-filled polygons.
By the way: You can also en-/disable the filling ...
Old timers might grumble about "etchant traps" ... acute angles can hold acid (well, FeCl) long enough to eat through the track - or not, depending on who makes the PCB for you. Consult with them if you are worried.
But I was downvoted for pointing that out in a previous answer, so at least somebody thinks that's no longer a problem.
As far as the signal ...
The primary advantage of a Manhattan route is that it can always be completed. You just need to have enough board area to accommodate all of the traces — but otherwise, you'll never find yourself unable to complete a route. This can be important if you need to get a layout done on a fixed schedule — the amount of work is roughly proportional to ...
In general, a device that connects N inputs to N outputs simultaneously is called a crossbar switch.
As long as all the signals are digital unidirectional signals, such as the signals on a few SPI buses,
a FPGA can be configured to dynamically route any of N inputs to any of N outputs.
If N is small enough, you might also be able to do this with some other ...
For a 2-layer board its pretty common to have one dedicated GND layer and use the other layer for all signals and power. In any case, prevent long traces on the GND layer, otherwise you may have unnecessary long GND return paths (due to the split GND plane/islands).
For multi-layer designs, its good practice to have at least one 100% dedicated GND layer ...
This is not intended to be a complete answer rather it's a useful hint at what designers do when complex clock distribution is required. (courtesy of TI source) showing bad and good clock layout design : -
Regarding the signal it doesn't matter.
The sharp angle might cause an acid trap, but with the trace width you are using should not be a problem.
I would have routed horizontaly from the SMD pad to the vertical trace making a right angle.
For a simple two-sided board, start by creating a ground polygon on the whole bottom layer. The trick then is to get Eagle to route most of the connections on the top layer. To do this, make the cost of routing within a polygon high and the via cost low. Actually you want to start with parameters more likely to find a solution, then tighten up the ...
If the width/thickness of the track can carry the current
The clearance between track and pad can withstand the voltage difference
Neither track or pads are sensitive analogue nodes
It's probably OK
My take is that caution applies primarily in situations with power filter capacitors run at mains-like voltages (160/320V bus), but they didn't bother to qualify it. Such caps are typically through-hole. Imagine the capacitor leaking and the board burning..
The electrolyte could allow more than enough conduction to cause a lot of havoc, but not enough ...
In general - yes. 100 kHz signal is very forgiving. Make sure to route both SDA and SCL in a similar fashion, close together.
Also keep in mind the I2C total capacitance limit of 400 pF (you could run into that issue if the traces were really long).
What you're looking for is called a "crossbar chip". Since this is a fairly inefficient way to use silicon resources, the emphasis these days seems to be on using such chips to route very high speed LVDS signals.
Recent versions of Altium allow any-angle-routing. While routing, just click Shift+Space until the routing mode changes to any-angle. I'm pretty sure this has been supported at least as long as the program has been called "Altium".
Is there a way to modify already existing tracks in an any-angle way? (Other than deleting and remaking them?)
I'm not sure ...