How to fix the compilation error in protel

1.The footprint of the component is not defined in the schematic.

Error message: footprint not found in library; component not found. As shown in the error in Figure 2 and 23 above.

Error cause: Since the footprint of the component is not defined in the schematic, the software cannot find the footprint of the corresponding part when loading the netlist in the PCB.

Solution: Open the netlist file to see which components are undefined, then find the corresponding component in the schematic, double-click the component, and fill in the corresponding footprint in the footprint bar in the properties dialog.

The name of the package definition does not exist.

Error message: footprint xx not found in library (there is no xx footprint in the component footprint graphics library); component not found. As shown in the error in Figure No. 3 and No. 26 above.

Error cause: The corresponding PCB library is not called in the PCB file or the component name in the PCB library is different from the name defined in the schematic.

Solution: Check whether all the required PCB libraries have been called in the PCB file, and check whether the package name of the component in the schematic is the same as the name of the PCB component library.

3.The component pin name is different from the package pin name in the PCB library.

Error message: node not found (no pads found). As shown in the error in numbers 19 and 24 in the figure above. Cause: The pin name of the component is different from the pin name of the package in the PCB library.

Solution: You can make the pin names of the components in the schematic library or PCB library consistent with each other.

4.The number of pins in the component in the schematic is greater than the number of pins in the PCB package.

Error message: node not found (no pads found). As shown in the error in Figure No. 22 above. Error cause: The number of pins of the component in the schematic library does not correspond to the number of pins in the package in the PCB library.

Solution: Go back to the schematic and redefine the footprint of the component. Make the number of pins of the component consistent with the number of pins and the pin name of the package.

5.Duplicate component designators.

This type of error is not prompted, and it is often more subtle and difficult to detect. Error cause: Duplicate component designators.

Workaround: Go back to the schematic and modify the duplicate component designators. Netlist mount errors occur frequently, mainly with regard to encapsulation errors.

When you find an error, you should browse it first and then eliminate it. If the macro command is executed in an orderly manner, if the previous macro command is wrong, it will cause subsequent errors. Troubleshooting should get to the root cause so that the problem can be solved quickly and effectively.

At the same time, it is necessary to be as standardized and careful as possible when designing schematics and PCB component libraries to reduce the occurrence of errors.

Problems include: unconnected net designators, unconnected electrical wiring, duplicate device names, non-driver sources connected to the input pin, or not connected (either due to incomplete libraries or forgotten connections).

Protel 99se does not have a compilation function, this is an error message that appears after creating a netlist, it is not called compilation.

The prompt has already told you that there is an error in component C1, and the library in which your component C1 is placed from, open that component library, find component C1, and look at the parameter settings of the pins, there is an error.

The network has the same name, and a schematic diagram is required. Press Ctrl+F to find the network with the same name and modify it.

Delete it and reconnect it.

Network errors, depending on what the error is.

1. The two components in SCH have the same number, the PCB only recognizes the earliest component, and the other component has different pin wiring, and there will be network errors, which is the most common. Therefore, in the SCH window, you should carefully check the list of components, and there can be no components with the same number.

2. The number of component pins in SCH is greater than the number of component pins in PCB, and the name of the component pins in SCH is inconsistent with the name of PCB.

3. The network identifier has a name that conflicts with the system, and this situation needs to be replaced with another letter to solve it.

As for the capitalization issue mentioned upstairs, it doesn't exist in Protel.

1. You need to check the description of the error report. Logically speaking, this problem will not occur, unless the name of your network ID is inconsistent in your diagram, such as a case issue.

2. It's best to see what the report says, and you can change it according to that.

The error shows that there is no driver, there are two reasons, one is that your software is not fully installed, and the other is that your file is not included in the current project, it is recommended that you check these two aspects.

There is no driver source;

Check the properties of the corresponding component and change the pin type.

You say it can be compiled on someone else's machine? Does that also have something to do with your software, is his software version the same as yours? It is recommended to check the pin type first.

has no drive, probably because you didn't create a project, but created a new schematic. You try creating a new project and saving it, adding your schematic to it, and compiling it.

There are two main possibilities for creating a new schematic error:

1. The version you installed is of poor quality or incompatible with your system, especially the latter. For example, DXP2004 can't work well under Win7, and there are many functions that can't be released. The best thing to do is to check the compatibility between the version and your operating system.

Generally speaking, DXP 2002 and 2004 are suitable for XP systems, and it is best to use AD or above with Win7 or above, such as or. If it has been installed and confirmed that compatibility is not a problem, then it may be a version problem, and the way is to uninstall it and reinstall it.

2. Another possibility is a license, both Fortel and Altium Designer require a license, but this license consists of two types, one is a network type (float) and the other is a stand-alone model. It's best to use the latter, and when you use it, it's best to use the window's built-in firewall to block it from accessing the network.

Your problem, most likely incompatible.