fritzing-app
fritzing-app copied to clipboard
fritzing
drc should check that there's no silkscreen intersecting copper pads
From [email protected] on October 15, 2010 06:02:20
What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.
Original issue: http://code.google.com/p/fritzing/issues/detail?id=1270
From [email protected] on October 15, 2010 03:05:18
could handle this by rendering silkscreen and copper layer to a bitmap, where each layer is transparent and monocolor (i.e. one is red, one is blue). Then BLT one image over the other and look for purple.
From [email protected] on October 15, 2010 03:15:02
Just to be clear, silk over traces is fine but silk over pads is a problem as this will cause messy issues with soldering. A shortcut would be to make sure silkscreen is always on top soldermask.
From [email protected] on January 04, 2011 04:09:08
Could use the new tiling approach for this: as usual, tile the plane from connectors to start out, but don't yet add the existing traces to the tilespace. Then render the silkscreen layer into a bitmap and convert that to rectangles (similarly to how the border is being dealt with). Then check that none of the rectangles overlaps.
From [email protected] on January 27, 2011 01:28:57
Not sure the approach in comment 3 works because connectors are treated as rectangles rather than circles, and since bitmapping the silkscreen might eliminate even more curves. Thus rectangles would overlap rectangles, even though the actual curved surfaces might not. So I think it's back to the idea in comment 1.
From [email protected] on September 02, 2011 00:37:54
gerber export should also clip silkscreen from pads
Summary: drc should check that there's no silkscreen intersecting copper pads
Cc: [email protected]
Labels: -Priority-Medium Priority-High
From [email protected] on September 02, 2011 02:24:53
DRC should not show this as an error, only as a warning (provided that the Gerber output will clip it anyway).
From [email protected] on February 25, 2012 13:18:35
Using the code that implements comment 6 raises an issue. This code subtracts the mask layer from the silkscreen layer. Many core parts, such as the resistor, have silkscreen imagery that extends right to the copper, so these parts would trigger a warning. Should the code only subtract the copper layer, or should we revise a bunch of parts?
From [email protected] on February 25, 2012 13:19:10
Status: Started
Labels: -Type-Defect Type-Enhancement
Remove imported label. Add pcbview. And I would remove the priority high. It seems like a low priority enhancement
