While checking some code generated by the surfacing tool I noticed that the dimensions and the minimum X and Z are wrong. It looks like gSender just scans the file and uses the smallest value found for each axis as the minimum. That doesn’t work with relative moves in the gCode. gSender 1.17 Windo…

As you saw in your edit, we’ve fixed this in Edge :+1: . Dimensions/bounding box was previously grabbed during the file estimation parser which has a small bug in it, but that was rolled into toolpath parsing and now accounts for relative positioning correctly.

Wrong dimensions shown in gSender

gSender 🐛 Bug

NeilFerreri May 10, 2023, 5:32am 2

Yes, makes me nervous everytime I use the surfacing toolpath generator.