Check project - Revision history

Harald Friedrich: /* SMD pad with drillhole */

2026-01-23T10:34:45Z

SMD pad with drillhole

← Older revision		Revision as of 12:34, 23 January 2026
Line 95:		Line 95:

	Caution: If this hole is drilled through completely and copper is present on another layer, '''a shortcut can be the result!''' Delete the drill hole by hovering the cursor upon it and click [[M11]]. Change the drill hole diameter to zero. If you have placed the drill intentionally, please ignore the message.		Caution: If this hole is drilled through completely and copper is present on another layer, '''a shortcut can be the result!''' Delete the drill hole by hovering the cursor upon it and click [[M11]]. Change the drill hole diameter to zero. If you have placed the drill intentionally, please ignore the message.

			However, the error message may also occur if a via is placed anywhere in an SMD pad. If such a via is not plugged or capped, capillary action can cause solder paste to be drawn away from the pad during heating (reflow). This can lead to a cold solder joint.

			For the component belonging to the SMD pad, the property “ALLOW_HOLE_IN_SMD” with the value “TRUE” can completely prevent this check.

	=== Symbol outdated ===		=== Symbol outdated ===

Harald Friedrich: /* NC connected */

2025-03-06T18:03:23Z

NC connected

← Older revision		Revision as of 20:03, 6 March 2025
Line 311:		Line 311:
	=== NC connected ===		=== NC connected ===

	A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br>		A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br><br>

	=== More signal islands than reference symbols ===		=== More signal islands than reference symbols ===

Harald Friedrich: /* NC connected */

2025-03-06T18:03:11Z

NC connected

← Older revision		Revision as of 20:03, 6 March 2025
Line 311:		Line 311:
	=== NC connected ===		=== NC connected ===

	A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.~~<br><br>~~<br>		A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br>

	=== More signal islands than reference symbols ===		=== More signal islands than reference symbols ===

Harald Friedrich: /* NC connected */

2025-03-06T18:03:01Z

NC connected

← Older revision		Revision as of 20:03, 6 March 2025
Line 309:		Line 309:
	[[Image:Pruefen5_e.png\|none]]<br><br>		[[Image:Pruefen5_e.png\|none]]<br><br>

	== NC connected ==		=== NC connected ===

	A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br><br><br>		A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br><br><br>

Harald Friedrich: /* Not connected */

2025-03-06T18:02:41Z

Not connected

← Older revision		Revision as of 20:02, 6 March 2025
Line 308:		Line 308:

	[[Image:Pruefen5_e.png\|none]]<br><br>		[[Image:Pruefen5_e.png\|none]]<br><br>

			== NC connected ==

			A pin whose connection function is set to NC (Not Connected) is nevertheless connected. This is not necessarily an error. Pins that are actually NC are often connected anyway for EMC reasons or for shielding. You could then set the connection function of the corresponding pin to Passive, for example.<br><br><br>

	=== More signal islands than reference symbols ===		=== More signal islands than reference symbols ===

Harald Friedrich: /* How to manipulate the size of the error markers */

2023-07-26T05:45:03Z

How to manipulate the size of the error markers

← Older revision		Revision as of 07:45, 26 July 2023
Line 59:		Line 59:

	[[Image:errormarkers.png\|none\|Size of error markers]]<br><br>		[[Image:errormarkers.png\|none\|Size of error markers]]<br><br>

			== Ignore spacing ==

			<br>As of V32, the check for spacing to other signals can be disabled for individual elements. This is interesting e.g. with an existing bridge in solder jumpers. If there is a standard connection in the jumper, which can be optionally scratched away later, then the check at this point always threw an error message because of a spacing violation:<br><br>
			[[image:IgnoreSpacingEN.jpg]]<br>Ignore spacing<br><br>
			A lightning bolt symbol appears in the right margin to additionally illustrate the danger of this checkbox.<br><br>

	== The meaning of the error messages ==		== The meaning of the error messages ==

Harald Friedrich at 04:03, 19 February 2020

2020-02-19T04:03:06Z

← Older revision		Revision as of 06:03, 19 February 2020
Line 131:		Line 131:

	Solution: Delete the signal segment, double click REF symbol (GND), change signal name to GND, connect new. Do a project reorganization (menu Actions) in order to make the error marker vanish, and do a project test again (menu Actions).		Solution: Delete the signal segment, double click REF symbol (GND), change signal name to GND, connect new. Do a project reorganization (menu Actions) in order to make the error marker vanish, and do a project test again (menu Actions).


	=== Track too thin ===		=== Track too thin ===

	The prescribed track width is not reached. This value is requested as minimum width in the signal (schematic) or directly in the check dialog on the upper right. A copper layer can also require its own minimum width. The error message can occur with individual track segments or with signal polygons whose filling width is too small.		The prescribed track width is not reached. This value is requested as minimum width in the signal (schematic) or directly in the check dialog on the upper right. A copper layer can also require its own minimum width. The error message can occur with individual track segments or with signal polygons whose filling width is too small.


	=== Bridge missing in schematic ===		=== Bridge missing in schematic ===

Harald Friedrich: /* Track too thin */

2020-02-19T04:01:56Z

Track too thin

← Older revision		Revision as of 06:01, 19 February 2020
Line 134:		Line 134:
	=== Track too thin ===		=== Track too thin ===

	The track width ~~in the layout~~ is ~~alerted too thin because it goes under the value calibrated in the Check Project dialog~~. This value ~~also can be set~~ in the signal ~~properties~~ (schematic) as minimum ~~track~~ width. ~~Highlight the complete~~ signal ~~and press keyboard key [e] for '''e'''dit. Now set the value for the track~~ width ~~higher than the one required in your checking routine~~.		The prescribed track width is not reached. This value is requested as minimum width in the signal (schematic) or directly in the check dialog on the upper right. A copper layer can also require its own minimum width. The error message can occur with individual track segments or with signal polygons whose filling width is too small.


	=== Bridge missing in schematic ===		=== Bridge missing in schematic ===

Harald Friedrich: /* Drillhole in SMD pad */

2020-02-11T14:33:49Z

Drillhole in SMD pad

← Older revision		Revision as of 16:33, 11 February 2020
Line 84:		Line 84:


	=== ~~Drillhole in~~ SMD pad ===		=== SMD pad with drillhole ===

	If a pad is placed upon a single layer lower than 100, for example only on layer 16=copper top or only on layer 2=copper bottom, it indicates a SMT constellation. So this is not a pad for a wired component where the pad would be on layer 100=through all layers. It is not a padstack too, which are defined on layers higher than 100. So if there is a drill within such a SMT pad this message appears.		If a pad is placed upon a single layer lower than 100, for example only on layer 16=copper top or only on layer 2=copper bottom, it indicates a SMT constellation. So this is not a pad for a wired component where the pad would be on layer 100=through all layers. It is not a padstack too, which are defined on layers higher than 100. So if there is a drill within such a SMT pad this message appears.

Harald Friedrich: /* Output error */

2019-09-04T08:07:16Z

Output error

← Older revision		Revision as of 10:07, 4 September 2019
Line 226:		Line 226:
	=== Output error ===		=== Output error ===

	An error message referring to the schematic. One signal either is fixed to several output ~~pins~~ or ~~to an output pin and a~~ supply pin. ~~In other words: several~~ output ~~pins are connected to a signal at the same time~~ or ~~to an output pin as well to a~~ supply ~~pin~~.		An error message referring to the schematic. One signal either is fixed to several output or supply pin. A signal can only have one output <b>or</b> one supply.