Closed Festivejelly closed 7 months ago
@Festivejelly there are different approaches here but we're stuck with the one we have for NanoEls - it's too late to change.
Lathecode isn't meant to be used with GCode coming from other places. If you want to modify H4 GCode sender https://github.com/kachurovskiy/nanoels/blob/main/h4/sender.html to be able to post-process inserted GCode e.g. invert one or both axes before sending - it could be one of the solutions. Or maybe https://festivejelly.github.io/LatheGcodeVisualiser/ would be the place to do it.
Thanks!
I agree, after a bit more reading it seems that lots of contollers/software do it differently. And tbh the fusion 360 post processor could be modified to achieve this.
To me logically your system makes more sense because Z+ is moving into the work. Same as with X.
I'll write a little tool in the visualiser to be able to post process fusion 360 nc files.
It seems on the Nano ELS the Z axis moves towards the chuck in the positive direction, same for the generated lathe code.
But as far as im aware the Z axis positive should always be facing the tailstock:
This issue was highlighted when I started trying to generate gcode with fusion 360.