Recently I saw a PCB which was all Ground and other Nets were Routed inside that. I found out that in order to do that (In DXP software) you have to do as following:
But the question is what is the reason of doing that?
Is that recommended to do it for all kind of circuits at all? Is that possible to make it all VCC? what would be the differences?
You usually do that in multilayer designs where you designate specific layers to certain power nets such as 3V3 or GND. the intended goal is to make the supply and return path of the current as short as possible (also, the two layers form some kind of small capacitance). If it's on the outside layers, it's sometimes done to block RF from leaving the inner layers. Also, it's nice for production since it reduces the amount of copper which needs to be etched away.
Well, most of all: it's a combination :-)
In Altium you might not want to use fills but instead you will be using polygons where you can specify the connect style (if you want the connection to be a thermal relief). Also, using the Layer Stack Manager you can specify specific layers to be power planes which basically makes them "inverted". So as long as you do not draw a line on such a layer, the full layer will be connected to a specific net. By drawing lines (thereby separating two areas) you can create so called split-power planes.
Ground planes are pretty common in PCB design. They act as shielding from outer electromagnetic radiation, therefore reduce noise cached from the outside. Also tend to reduce crosstalk when ground trace is placed between signal traces. The drawback of such planes is that they introduce higher capacitance between signals and the ground, what is relevant for high frequency circuits. That is why hatched pours are also used as introduce smaller capacitance.
Regarding Supply planes they effectively act as wide traces, improving current handling and reducing voltage drop on such trace. If such plane provides supply to other layer, number and size of connecting vias has to be taken into account as can be bottleneck of current path.
