Please fill this out:
pcb2gcode version (run pcb2gcode --version to see this):
2.2.0
Git commit: latest
Boost: 106700
Gerbv: 2.7.0
Geos: Not installed
What did you try (include command-line arguments):
pcb2gcode --front pinpad-F_Cu.gbr
What happenned:
The gcode produced probes 70 points; #500 to #569, but then uses eg #578 during milling.
This appears to be because workareaLenX is calculated, but then the offset is added before milling (at least setting offset=0.0 removes the problem)
or
130c130,131
< workareaLenX = ( workarea.max_corner().x() - workarea.min_corner().x() ) * cfactor +
---
> //IAN
> workareaLenX = 1.0 + ( workarea.max_corner().x() - workarea.min_corner().x() ) * cfactor +
132c133
< workareaLenY = ( workarea.max_corner().y() - workarea.min_corner().y() ) * cfactor +
---
> workareaLenY = 1.0 + ( workarea.max_corner().y() - workarea.min_corner().y() ) * cfactor +
What did you expect to happen:
Variables/Registers to be set before use.
Please attach your input files and relevant output files and images. Don't forget to include your millproject file and gerbers!
pinpad-F_Cu.gbr.txt
millproject.txt
output.ngc.txt
Please fill this out:
pcb2gcode version (run pcb2gcode --version to see this):
2.2.0
Git commit: latest
Boost: 106700
Gerbv: 2.7.0
Geos: Not installed
What did you try (include command-line arguments):
pcb2gcode --front pinpad-F_Cu.gbr
What happenned:
The gcode produced probes 70 points; #500 to #569, but then uses eg #578 during milling.
This appears to be because workareaLenX is calculated, but then the offset is added before milling (at least setting offset=0.0 removes the problem)
or
What did you expect to happen:
Variables/Registers to be set before use.
Please attach your input files and relevant output files and images. Don't forget to include your millproject file and gerbers!
pinpad-F_Cu.gbr.txt
millproject.txt
output.ngc.txt