Gerber file Misplacing top silkscreen

[Anonymous]

Hello all,

I am making a four layer board and have ran into an issue I have never had before. When using the 'generate CAM data' button in the toolbar, the Gerber file misplaces my silkscreen. Any fix would be greatly appreciated!

Some additional information: I am using sunstone 4 layer eagle DRC rules. (I have used them in the past without this problem)

Gerber outputtPlace tName tValue... and more in Eagle

[one-of-the-robs]

Try a different viewer. There are some online viewers that are known to produce utter rubbish.

I use gerbv but there are several other free Gerber viewers available.

[Anonymous]

I discovered something was wrong when I went to purchase the board from JLCPCB. Unfortunately, I don't think it is the viewer.

JLCPCB

[one-of-the-robs]

OK, check the settings you get from those DRC rules and in the manufacturing tab. It looks like the silk screen Gerber is mirrored, which I can see no good reason for as it's a top-side one.

[Anonymous]

I messed around in the CAM processor for a while and also tried loading different DRC rules. For some reason when I have a 6-Layer board everything comes out okay. Then I manually remove the inner two layers while still using the 6-layer DRC and then the silkscreen disappears similar to before with the 4-layer DRC I was using. I am not sure why I am having trouble with the silkscreen on 4 layer boards specifically. Below I detailed the steps that ended up fixing it. Note: Vertically mirroring the 4 layer DRC silkscreen did not fix the problem.

JLCPCB Gerber Viewer 6-Layer CAM JobJLCPCB Gerber Viewer 6-Layer CAM JobEagle PCB preview with the 6-Layer DRC manually changed to 4 layersEagle PCB preview with the 4-Layer DRCCam Processor with 4-Layer DRC shows the top silkscreen mirrored verticallyCam Processor with 6-Layer DRC shows the top silkscreen in the correct orientation6 Layer DRC stackupManually removing 2 layers6-layer DRC with 2 layers removed. Top silkscreen again mirroredMirroring the silkscreen vertically appears to fix itApparently this time it did fix it. That was unexpected.