Bernd K.

The reason why it never came to my mind to implement this is that from the very beginning when I started developing this I always had a separate terminal window...

Ok, I have found how this is meant to be used: There is a setting for each axis where I must enter the number of a digital input. This is...

When the number of inputs/outputs can change for different boards it should probably not be defined in a global configuration file and should be moved into the board-specific headers. When...

Is there a computational cost associated with leaving all 6 motors enabled or is it just the size of the binary? I didn't notice any dramatic differences at all. If...

I found the reason: The attached patch will fix both: the probing and the homing problems for U,V,W, Please merge. ```diff diff --git a/g2core/cycle_probing.cpp b/g2core/cycle_probing.cpp index 3f3db80f..f8ab9423 100644 --- a/g2core/cycle_probing.cpp...

No need to lose sleep over it, I can't continue to work on my machine for the next seven days anyways, the most important thing is to know that it...

How about rewriting the above function like this? ```C static int8_t _get_next_axis(int8_t axis) { const int8_t homing_order[9] = {AXIS_Z, AXIS_X, AXIS_Y, AXIS_U, AXIS_V, AXIS_W, AXIS_A, AXIS_B, AXIS_C}; if (axis ==...

It moves with U_FEEDRATE_MAX until it hits the limit switch, then the motor stops and the machine is frozen, homing sequence is stuck at this point and never ends, needs...

The function above seems to return correctly, if I do for example g28.2 x0 z0 u0 it will correctly home z, then x, then start moving u (but with the...

This is the output (in text mode) when I am trying to home U ``` g28.2 u0 g2core[mm] ok> A position: -13.737 mm Feed rate: 200.000 mm/min Velocity: 4000.000 mm/min...