Halscope scaling - Axis Acceleration behaviour

Tommy thanks for checking that in a SIM. Saved me a job.

If you look at your formula (iv) V = at we are solving for a (eg. a = V/t) and we have V and t from the plot so to me the maths is sound...
and validated by a couple of online calculators. Just everything must be converted to SI units (eg metres, not mm)

I think its just we don't understand how Linuxcnc works. I suspect this is an easy run with no segments for the look ahead to look at so it idles. I know when I spent hours calibrating my Z with a dial indicator with the torch going up and down to check for missed steps, everything came undone in the real world. I took that to mean LCNC was accelerating harder than when I did the same sort of motion.we are doing here. It would be interesting to try the same with a 45 degree angle so both axes are moving equally. MAybe the other half should come from the Z axis.

Strange, I was using Gcode... And I got 50%
Its hard to work out from the screen dump, how far over the max accel did it go?
Actually when I think about it if X & Y are both moving at Max-vel for their axis, the total accel has to be over the individual max-vels

That does make sense, if X & Y are both acellerating at 508, the resulting total Accel has to be higher! You could work it out with resolution of forces but my brain hurts. It should be a 45 degree angle so I think its something like 508 * sin(45) +508 * cos(45) but that does not make it to 879

if all 3 axis accels are 508, and the overall acceleration is not bounded,
say by MAX_LINEAR_ACCELERATION, acceleration in all three axis
can be sqrt(3)*508 =879.88

Oops. I left the Z axis out!

The ini settings are used for GCode, MDI commands do seem to use 1/2 of the acceleration settings

Yeh I had a thought overnight. I was using relative commands so maybe they are planned the same way as MDI commands.

Also there is Simple trajectory planner used for jogging. I wonder if it used for MDI and relative commands? More testing later today.