Start a new topic

EPS (Postscript) to Gerber conversion. Why weren't all the round pads converted to flashes on import?

EPS (Postscript) to Gerber conversion. Why weren't all the round pads converted to flashes on import?
1 Comment

[QUOTE]When I import the attached eps file and click the box for flashing while doing so  --- not all the circles get flashed, some stay as polygons.

I seem to be able to select all those that were not converted by using "convert to flash" selective and specifying eclipse.

Is there a faster way?  And why weren't all the round pads converted to flashes on import?

Fab3000 is amazing.[/QUOTE]


Thanks for sending me a sample EPS file.  Ghostscript performs the parsing and generates the boundaries which are in turn used by FAB 3000.  The 'real problem' with the inconsistent flashing arises from the unnecessary complexity of your generated Postscript files.

For example, here's the standard postscript code to draw a single circle:

351 260 0.8 0 360 arc closepath

Note: Circle center (351,260) with radius 0.8; units are in points.


If you look at your generated Postscript file, a single circle will appear as this complex sequence  (this is a circle located at 351,260  radius 0.8 which did not flash).

@rax %Note: Object
350.20091 259.01178 351.84983 260.66069 @E
/$fm 0 def
 0 O 0 @g
[ 1.00 0.00 0.00 1.00 0.00 null ] set_fill_color
351.02551 260.66069 m
351.02636 260.66069 L
351.25398 260.66041 351.45978 260.56800 351.60860 260.41918 C
351.75742 260.27036 351.84926 260.06485 351.84983 259.83808 C
351.84983 259.83808 L
351.84983 259.83638 L
351.84983 259.83581 L
351.84954 259.60847 351.75713 259.40239 351.60803 259.25329 C
351.45950 259.10476 351.25370 259.01235 351.02665 259.01206 C
351.02693 259.01178 L
351.02551 259.01178 L
351.02466 259.01178 L
351.02466 259.01206 L
350.79732 259.01206 350.59124 259.10447 350.44214 259.25386 C
350.29361 259.40239 350.20148 259.60819 350.20091 259.83496 C
350.20120 259.83496 L
350.20120 259.83638 L
350.20120 259.83723 L
350.20148 260.06457 350.29361 260.27065 350.44271 260.41946 C
350.59181 260.56800 350.79704 260.66013 351.02353 260.66069 C
351.02381 260.66069 L
351.02551 260.66069 L
@c
F


As you can see from the unnecessary complexity from you Postscript file, it's even difficult for me to manually follow that code & determine if it will result in a circle.  Which means that complex code makes the circle detection algorithm (within ghostscript) much less likely to succeed. 

Note:  The only reason FAB 3000 can manually detect those circles (using convert to flash command)  is because you have chosen a command that specifically tells FAB 3000 to create a circle out of any boundaries you selected.  You could select any polygon shape (like an octagon, star, etc.) and if you tell FAB 3000 to make it a circle -- it will.

In the end, keeping data simple results in better efficiency.

Thanks again.
Login or Signup to post a comment