Problem: slow homing speed. `seek_mm_per_min` has no effect about fluidnc HOT 2 OPEN

Try jogging the axis at the same speed as your seek rate. How does that compare to your homing speed.

BTW. Do you always use mm or sometimes inches?

Axes XYZ should be used for rotary axes especially if you use inches.

from fluidnc.

I set the axis/z/max_rate_mm_per_min to 1400.000000 and jogged the axis. If I press the move button for the z axis on the webUI I can see that the $J=G91 G21 F100 Z10 command is sent and the axis moves slowly, similarly to when the homing command is send. However, if I send, for example, the Z100 command, the axis moves much faster.
I observe the same behaviour with the settings I provided above.

I am not sure if this is relevant, but when running the Z<some_value> command I can see in the terminal that the FS (feed speed?) is set to the value of axis/z/max_rate_mm_per_min

<Run|MPos:0.000,0.000,87.461,0.000|FS:1400,0>

, but when I start the homing procedure, the FS is set to 858

[MSG:DBG: Planned move to 0.000,0.000,10999990.000 @ 1400.000]
<Idle|MPos:0.000,0.000,-9.991,0.000|FS:858,0>
<Home|MPos:0.000,0.000,-7.831,0.000|FS:858,0|WCO:0.000,-27.000,0.000,0.000>
<Home|MPos:0.000,0.000,-4.411,0.000|FS:858,0|Ov:100,100,100>
<Home|MPos:0.000,0.000,-0.990,0.000|FS:858,0>

If I move the Z axis on the webUI the FS is 100 (I assume because of the command $J=G91 G21 F100 Z10 )

<Jog|MPos:0.000,0.000,0.000,0.000|FS:100,0|Ov:100,100,100>
<Jog|MPos:0.000,0.000,-3.420,0.000|FS:100,0>
<Jog|MPos:0.000,0.000,-8.401,0.000|FS:100,0>

I should note again that the movement speed of homing and jogging via the webUI is similar (and not 8x greater).

I am not sure if I totally understand the question. For all axis except Z I am using mm. For Z I want the units to be degrees of rotation of the plate that is connected to the Z axis motor (via a 1:4 gear ratio), similarly to how your String art machine functioned (if I understood that setup correctly).

from fluidnc.