I recently started using Eagle and the Eagle Board input widget and was able to route out a small relay control board to control my spindle and vacuum from the tinyg board. The layout used some polygon elements to create some larger pours and the outlines were successfully created by the widget. I am creating another board to do some level translation and none of the polygon elements are being properly isolated by the widget. I reduced the schematic and layout down to a few elements and still have the problem.
The polygons appear properly filled in Eagle, but not in the widget. The picture is from a windows 8 install running all the latest versions of eagle/Java/chrome. On my MAC with Safari, the polygons show up as grey filled, but the widget generated the same G-code. The polygons are “named” the same as the rest of the net. The result is the same if the polygon fill is done with thermals enabled.
Any thoughts on what is going wrong?
I really appreciate all of the awesome work being done on ChiliPeppr. You guys rock!
The Eagle BRD widget does try to match up the polygon signal name to the overall signal name to know whether to isolate the polygon or to combine it. Are your signal names the same? Maybe show us a screenshot of you hovering over the polygon and then over the pad as well?
Also, it is very possible the polygon rendering algorithm has bugs. Polygons are a very difficult area to deal with as there’s no documentation or standard on how Eagle handles them, and so it’s just a trial/error process of trying to match Eagle’s behavior. You may have found a new behavior scenario I never tested.
Thanks John. I am certain the polygon is tied to the same net, it looks okay in the .brd file:
If you look closely at the picture, the edge of the polygon is detected and creates a cut where it overlaps something else. The pads completely surrounded by the polygon are not cut out, but neither is the edge of the polygon itself.
If the polygon is not named the same as the component net, the pads are isolated and the edge of the polygon is not routed.
I have compared the .brd files between the one that does not work and one that work and the only thing that pops out to me is that the one that works is on a .01 grid and the one that doesn’t is on a .05 " grid.
I have whittled the failing example down to two components and one polygon (15k) and can send it to you if that would help.
… Okay, problem solved. There needs to be a defining rectangle of the board outline on the dimension layer in order for any polygons to be properly outline routed in the board widget. This is not a requirement for any other element (?).
Ok, that makes sense that you need the board outline, but it would be nice if we told you that in the widget. Good catch. Also, i’m realizing that your stroke around your polygons is not being taken into account, so that’s sort of an issue as well.
