[BUG] movement too slow with G2/G3

[DerAndere1]

Did you test the latest bugfix-2.1.x code?

No, but I will test it now!

Bug Description

WITH SYNTAX G2/G3 X Y Z I J F THE AXIS DO MOVE BUT VERY SLOWLY

This potential bug was first reported by @printercnc here: https://github.com/DerAndere1/Marlin/issues/55#issuecomment-2067712328

Bug Timeline

unknown

Expected behavior

Feedrate should be accoring to parameter F

Actual behavior

Feedrate too slow

Steps to Reproduce

TODO

Version of Marlin Firmware

unknown

Printer model

custom

Electronics

unknown

Add-ons

unknown

Bed Leveling

None

Your Slicer

None

Host Software

None

Don't forget to include

• [X] A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

TODO

[printercnc]

you need to check this part

Suppose we have a cnc router like this, without ATC tool change, we will measure z0 with command G38 (G38.2, G38.3..)

Each replacement tool is tool number 0, if tool number 1 to measure the z0 plane works as shown, the following tools will measure according to the hard probe position mounted on the chassis. I'm in no rush, but I'm nervous every time you make another move, can't wait to test your improvements, I'll check those parts out. in my experience through old marlin versions, g38 only works with //#define Z_MIN_PROBE_PIN -1

[DerAndere1]

I corrected the comment about hotend offset. It should read "For the other hotends it is their distance from the extruder 0 hotend in positive axis direction."

I have not tested probing. but I still think the easiest way is:

• never use tool 0 for machining. Ideally, tool 0 is the gage line / empty spindle. alterntively, tool 0 can be a probe or a rigid master reference tool that is never used for milling.
• Make sure that your NOZZLE_TO_PROBE_OFFSET is correct. If you use the device shown in picture 2 of your last comment, I think you need //#define PROBING_TOOL 0, #define NOZZLE_AS_PROBE and #define NOZZLE_TO_PROBE_OFFSET {0.0, 0.0, 0.0, 0.0, 0.0} for a 5 axis machine.
• Use M218 or G10 L1 to set hotend offsets (tool offsets) based on your measurements.

Depending on your measurement procedure, you might get different raw values from those measurements. From those raw measurements you have may have to substract or add other offsets to calculate distance of each tool tip from tool 0. But the final values you define with M218 or HOTEND_OFFSET_Z MUST correspond to the distance of the tool tip from the tip of tool 0 in mm. E.g. if tool 1 is 10mm longer than tool 0, you need `HOTEND_OFFSET_Z {0, -10}. This is how Marlin works. References:

• https://marlinfw.org/docs/setting/extruder.html,
• https://marlinfw.org/docs/configuration/configuration.html#hotend-offsets

If you want to use tool 0 for machining, you have to find your own solution. I cannot provide support for that.

[printercnc]

Maybe you don't understand my question. I downloaded the latest version, #define SPINDLE_FEATURE error appeared homeZ error I will check again why there is this error while I installed exactly the same marlin_bugfix version I am using.

[DerAndere1]

I recently added code to stop the spindle/laser at the start of a toolchange command (T...) and automatically restore the spindle/laser state after completion of the toolchange. That broke compilation with SPINDLE_FEATURE. This is fixed now with commit https://github.com/DerAndere1/Marlin/commit/0c23f49e5f5ef44e743defab0075dffda84d68cc

I cannot find a description of the homeZ error you get. Always copy exact error messages.

[printercnc]

Maybe I set the wrong value of the Z axis, I want the distance between the values ​​to be as short as possible but that's not possible.

error warning "G38_PROBE_TARGET requires a Cartesian machine." Can you completely remove it? Or every time I download your new update, I will manually remove this warning

[printercnc]

add this error

[DerAndere1]

"error: IsRunning was not declared in this scope" is fixed for me with commit https://github.com/DerAndere1/Marlin/commit/8a32e107c6bbc659953db5a5bd98a33f291d27e1

Regarding your mysterious "homeZ error": You can enable DEBUG_LEVELING_FEATURE and increase the detail of the logged information by sending Command M111 S38 before homing (https://marlinfw.org/docs/gcode/M111.html). If you send me a copy of the logged information, I might be able to help you