FEDEVEL
Platform forum

MichaelG237 , 11-12-2025, 03:46 PM

Hey,
I wanted to ask a question that I haven’t been able to find a clear answer to online, regarding netlist verification.
I wanted to hear what are other people method of doing the netlist check before moving to the layout stage.
Im currently using Siemens xpedition, but I’d be interested to hear about methods used in other tools like Altium as well.


At this stage, the goal is to ensure that all nets are correctly connected, named properly, and that there are no missing connections. I’ve been using three different approaches:

1. Quick Connection View from xpedition:
I generate the netlist in the tool’s output window and review each net one by one. Each net i click, takes me directly to the net in the schematic. The nets I’ve checked are highlighted in purple, but the challenge is that if the tool is closed, I lose track of progress, and there’s no formal proof that all nets were reviewed and it can be frustrating for big designs.


2. Printed Schematic Review:
With the exported netlist, I can print the schematic (usually on A3 paper) and manually mark each verified net in green and any issues in red. This method is less efficient and harder to manage for large designs.


3. Excel-Based Check:
I export the netlist to Excel and organize it into columns using a custom script. Then, I open the schematic PDF on another screen and go through each net row by row. I’ve added macros to quickly mark rows by color and filter by specific blocks (e.g., selecting “GND” shows all GND nets, or “U1” filters nets connected to U1).
This gives me a well-documented overview of verified nets and is easier to follow, but it’s still manual.

So I'd really be happy to hear what other people methods for improving the efficiency of this stage. Thanks in advance.

QDrives , 11-12-2025, 04:27 PM

So in Altium I use something comparable to what you have as point 1.
1) Validate the design (make sure you fix all errors and warnings first)
2) Using the Navigate mark a net in a color, like purple.
3) Validate each netlabel, port and pin as indicated by the navigator.
4) If correct, mark the net in the green color.
5) Go to the next net. When finished, all nets should be colored green.

Altium remembers the coloring, IF saved (project).
Alternatively for xpedition using hybernating. So do not close xpedition, nor the computer.

Robert Feranec , 11-12-2025, 11:24 PM

For simple schematic and cheap boards - I just build it, fix it and build again.
For complicated schematic I spend a lot of time by checking - can be week or more. It has several stages and several "point of views". For example: Initial check is to be sure all the pins in symbols have correct pin number and pin name - I print schematic and go through every single pin number and pin name. This is very important as the next checkings are based on the pin names in the schematic. Then there are more "point of views" for example I have a look at my schematic from reference schematics point of view (I compare if i followed it correctly), from datasheet point of view (go through pin descriptions and check if they are connected correctly), then maximum currents and power delivery view, power sequencing, voltage levels (checking if signals are using the same voltage levels), interface point of view (are signals of interfaces connected correctly e.g. swaping RX/TX, be careful with negative / positive signals, SDA SCL, ...), checking pull ups pull downs, etc ... To be sure I don't miss anything, I go through every single pin in the schematic and I have a look where each pin is connected. Takes a lot of time, but saves more time in case something would be wrong.

Robert Feranec , 11-12-2025, 11:24 PM

I have done a number of videos on this topic: https://www.youtube.com/@RobertFeranec/search?query=schematic%20check

Robert Feranec , 11-12-2025, 11:26 PM

Some time ago I also made a blog post about it, it can help you:

Robert Feranec , 11-12-2025, 11:26 PM

https://fedevel.com/blog/8-step-schematic-checking-procedure

MichaelG237 , 11-13-2025, 03:49 PM

I see, yes i try not to close it, but sometimes it just crashes for time to time