Start a new topic

My gerber files loaded fine into FAB 3000. Why are there some different dcode numbers being used?

My gerber files loaded fine into FAB 3000. Why are there some different dcode numbers being used?
1 Comment

My gerber files loaded fine into FAB 3000, but I noticed in some cases a different Dcode number is being used when I query the gerber geometries (traces, flashes). Why are there some different dcode numbers being used?


During gerber import FAB 3000 may optimize and transcode (i.e change the Dcode number defined in the original aperture list or gerber header to a different empty Dcode number).  This is common in most advanced CAM/gerber software tools, and in most cases it is almost impossible to load various aperture and gerber files without having to perform some type of transcoding.


TEST CASE:
A particular gerber file has Dcode 10 defined as "Circle 1mm" in the aperture list, however Dcode 10 may already be defined in FAB 3000 as "Circle 2mm" (from some other gerber file which has already been loaded); so now FAB 3000 must find and empty Dcode and transcode to that empty Dcode (say Dcode 30 depending on the situation). 

Note:  Nowadays with extended gerber formats like: 274X, Fire 9000, and ODB++ the actual Dcode number referenced is not of much concern anymore.

Login or Signup to post a comment