Skip to content

Absolute mode isn't sticky, leading to continuous relative/absolute transitions #74

@fake-name

Description

@fake-name

I'm doing some gcode generation that uses entirely absolute moves.

Every single move winds up surrounded by a G90/G91 pair:


G90 ;absolute
G1 X5.000000 Y5.000000 Z5.600000
G91 ;relative
G90 ;absolute
G1 X5.750000 Y5.000000 Z5.600000
G91 ;relative
G90 ;absolute
G0 X5.750000 Y5.000000 Z16.000000
G91 ;relative
G1 F3.0
G90 ;absolute
G0 X6.250000 Y6.000000 Z16.000000
G91 ;relative
G90 ;absolute
G0 Y6.000000 Z5.750000
G91 ;relative
G90 ;absolute
G0 X6.250000 Y6.000000 Z5.750000
G91 ;relative
G90 ;absolute
G1 X6.000000 Y6.000000 Z5.750000
G91 ;relative

Looking at the code, this seems to be because nothing can ever set the gcode writer to absolute mode other then an explicit call to absolute().

It seems to me that if you call an absolute move call, it should set the state to absolute and leave it there, until any call to a relative motion function.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions