Author Topic: GBR files  (Read 40460 times)

beikeland

  • Guest
Re: GBR files
« Reply #105 on: November 17, 2016, 04:12:55 AM »
Made a SOP14 adapter yesterday, Traces are coming out wider than "planned", do you think the solution is to enter a wider or narrower tool diameter in the software making the g-code? Seem to be getting the hang of the quality for applying the photoresist, exposure and etching now. Removing G0 moves helped a lot! Tried applying soldermask, but the openings for the SOP chip completely disappeared  so had to remove it again unfortunately.



Zax

  • T2Laser
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7308
    • View Profile
    • T2Laser
Re: GBR files
« Reply #106 on: November 17, 2016, 04:55:45 AM »
@beikeland, I have attached the G-code for the file you posted using the settings requested. I used resolution 0.1 or 10 lines per mm and did not add any vector trace to it. I would be interested if it is fine enough and without any edge issues.

Screenshot also attached so you can verify the size and pattern.

The updated T2Laser version was posted yesterday so Agastar and Kunaphil can test it also.


beikeland

  • Guest
Re: GBR files
« Reply #107 on: November 17, 2016, 06:04:34 AM »
From a distance it looks pretty good; but up close you see the jagged edges both partially due to the round beam, and the slight inaccuracies of the machines.

And you can always leave it to me to screw up, so I overlapped the two runs by offsetting it some 30+ mm in X instead of Y, and I left the laser centered on the first run when I changed the firmware leaving a big blotch in the center where the laser energized when flashing :/

Anyways, closeups attached. I think offsetting the scanning by a tool width and tracing the outline after would yield a much crisper outline, but for hobby use its probably not worth the effort.

Code: [Select]
1.1d.20161104
$0=10 (step pulse, usec)
$1=25 (step idle delay, msec)
$2=0 (step port invert mask)
$3=0 (dir port invert mask)
$4=0 (step enable invert, bool)
$5=0 (limit pins invert, bool)
$6=0 (probe pin invert, bool)
$10=2 (status report mask)
$11=0.010 (junction deviation, mm)
$12=0.002 (arc tolerance, mm)
$13=0 (report inches, bool)
$20=1 (soft limits, bool)
$21=0 (hard limits, bool)
$22=1 (homing cycle, bool)
$23=3 (homing dir invert mask
$24=100.000 (homing feed, mm/min)
$25=500.000 (homing seek, mm/min)
$26=100 (homing debounce, msec)
$27=2.000 (homing pull-off, mm)
$30=255 (rpm max)
$31=0 (rpm min)
$32=1 (laser mode, bool)
$100=80.000 (x, step/mm)
$101=80.000 (y, step/mm)
$102=250.000 (z, step/mm)
$110=4000.000 (x max rate, mm/min)
$111=4000.000 (y max rate, mm/min)
$112=500.000 (z max rate, mm/min)
$120=800.000 (x accel, mm/sec^2)
$121=800.000 (y accel, mm/sec^2)
$122=10.000 (z accel, mm/sec^2)
$130=150.000 (x max travel, mm)
$131=200.000 (y max travel, mm)
$132=200.000 (z max travel, mm)

edit: forgot the picture of the board :/
« Last Edit: November 17, 2016, 06:54:59 AM by beikeland »

beikeland

  • Guest
Re: GBR files
« Reply #108 on: November 17, 2016, 06:06:39 AM »
Hmm, looking at those pictures, would it be safe to assume my dot is quite oval seeing the traces are nice and thin along one axis but thicker along the other? The trace width is the same all over except the fake SMD pads for the headers.

Zax

  • T2Laser
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7308
    • View Profile
    • T2Laser
Re: GBR files
« Reply #109 on: November 17, 2016, 06:42:36 AM »
T2Laser already supports the vector outline after raster in the same G-code job, I just didn't select it.

beikeland

  • Guest
Re: GBR files
« Reply #110 on: November 17, 2016, 06:57:38 AM »
Then I think its should quite usable now, when you can manage to separate your X from your Y and stuff like that :D

Last think I could think of would be having opening where the should be holes according to drill files, to assist with manual drilling.

Kunaphil

  • Full Member
  • ***
  • Posts: 148
    • View Profile
Re: GBR files
« Reply #111 on: November 17, 2016, 08:00:16 AM »
beikeland,

the pictures you posted are almost  exactly what my results are.  I am sorry, I got home last evening too late  to take any pictures of my results.
Just got my home switches installed!👍

beikeland

  • Guest
Re: GBR files
« Reply #112 on: November 17, 2016, 08:15:11 AM »
Could you narrow it down? The microscope close up is probably close to as good as it gets anyway.

There is a wiggly part both on the T2 preview and final result, especially on the tracks running along the Y direction in middle, and I have no explanation for that. They are not part of the design in KiCad and they did not show up on the etched board I posted complete with components. My machine adds even more wavyness than what is shown on the T2 screenshot, and that will be fixed with new wheels.

I may have a feeling it has something to do with KiCad possibly exporting may segments instead of straight lines to help with auto-leveling features on CNC machines?

Zax

  • T2Laser
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7308
    • View Profile
    • T2Laser
Re: GBR files
« Reply #113 on: November 17, 2016, 08:25:16 AM »
I think those are artifacts of the vector to raster conversion.

It looks really clean on my screen as shown in this zoomed in picture.

In some cases I have found importing at 0.05 and then down-scaling the image to 0.1 improves the result, for the attached phono file (I turned off the aperture list to show what it looks like as vector, this is a setting in T2Laser and may be useful) it has many lines so doing this "trick" makes sure the result is completely filled solid. It probably doesn't matter to the end result.

beikeland

  • Guest
Re: GBR files
« Reply #114 on: November 17, 2016, 09:49:45 AM »
I'll be happy to run whatever g-code you want, to aid the testing. The dry film is quite inexpensive, and its good practice to get better at laminating the film on the bare PCBs :)

(Just keep in mind the general wobbliness of my laser for now:)

No need to actually etch the copper to see the results really.

Zax

  • T2Laser
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7308
    • View Profile
    • T2Laser
Re: GBR files
« Reply #115 on: November 17, 2016, 10:49:43 AM »
This is the same file and parameters except with diagonal engraving, as with the horizontal I do not see any anomalies (wiggles) in the traces or pads. Any shown on-screen are artifacts and not there when you zoom in.

beikeland

  • Guest
Re: GBR files
« Reply #116 on: November 17, 2016, 11:11:37 AM »
LW3 didn't like that, shows no toolpaths despite there being ample g-code in the file. Will look into it later.

Kunaphil

  • Full Member
  • ***
  • Posts: 148
    • View Profile
Re: GBR files
« Reply #117 on: November 17, 2016, 11:22:57 AM »
beikeland,

What are your recommended settings in T2?  I am so new to this that I am not sure as  to what and how to cut  these properly.
Just got my home switches installed!👍

beikeland

  • Guest
Re: GBR files
« Reply #118 on: November 17, 2016, 11:37:26 AM »
I do most of my work on Linux so T2 isnt't something I can use. Which is partly why I asked Zax to send me the g-code generated so I could  just run it.

And I use a much weaker laser, about 15mW now I think (gussing). But Zax posted "I used resolution 0.1 or 10 lines per mm" and it was run with F2500 and S128 (S128 is about 15mW, so with a 2.5w laser with somewhat linear TTL driver it would be between S1 and S2)

Zax

  • T2Laser
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7308
    • View Profile
    • T2Laser
Re: GBR files
« Reply #119 on: November 17, 2016, 04:53:26 PM »
I found some complex Gerber files online to test with the latest release (v1.3n) of T2Laser.