Skip to content

custom gcode capture needs to be as concurrent as possible #5

Closed

Description

@T3P3

Currently if you select "custom gcode" can run a capture move it appears to run them sequentially. running the same set of commands form the console (e.g.)

M569.5 P50.0 S20000 A0 R20000 D6913 V0 G1 H2 Y100

runs them more concurrently.

Activity

  1. chrishamm commented on Oct 8, 2026

    @chrishamm
    Contributor

    Fixed in 3.4.0. The recorder used to wait for the M569.5 reply and then send the move as a
    second command. It now sends both in one multi-line code, like your console example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions