Skip to content

Startup toolshift settings don't match default toolshift settings. #71

Description

@Ibot-11

What happened

The default toolshift settings after startup without performing the TOOLSHIFT_CONFIG macro do not match the default values set in TOOLSHIFT_CONFIG.
For example, the speed or Z hop is different (the most important thing I noticed).

What did you expect to happen

When I have done a print and want to change a single setting, I run TOOLSHIFT_CONFIG. Because the macro defaults are different, it also changes some other settings, causing unwanted and unexpected changes in settings.

How to reproduce

Start a print without TOOLSHIFT_CONFIG and start a print with TOOLSHIFT_CONFIG

Additional information

Can be easily fixed by adding a delayed gcode performing TOOLSHIFT_CONFIG on startup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions