I’ve recently received my “2021 M2 Automated Cutting Machine Kit” and am currently having fun setting it up and doing some initial trial cuts. Off the bat I noticed that the feed rate in the x-direction appeared to be slower than the y-direction, so today I took a bit of a deeper look into it.
Using the following g-code, I made 3x straightforward moves: one 500mm in the x-direction (0,0 to +500,0), one 500mm in the y-direction (+500,0 to +500,+500) and one 707mm long diagonally back to (0,0).
The intent here was to use a feed rate of 500mm/min for each of the 3x moves.
I then timed each move with a stop watch and calculated the corresponding feed rates. The results were:
Move 1: 72sec, 417mm/min
Move 2: 44sec, 682mm/min
Move 3: 92sec, 461mm/min
I thought this was a little strange considering:
- I requested 500mm/min
- The observed feed rate was not constant per move
I followed up with a second measurement - this time using 762mm/min (30in/min). The results this time were:
Move 1: 48sec, 625mm/min
Move 2: 30sec, 1000mm/min
Move 3: 60sec, 707mm/min
Changing the requested feed rate from 500mm/min to 762mm/min corresponds to a scaling factor of 1.524. The measured scalings per move were:
Move 1: 1.5
Move 2: 1.47
Move 3: 1.53
so even the scaling doesn’t look constant per move.
Has anyone observed this type of behavior before? I can’t imagine it’s intentional but being new to all this, perhaps I’m overlooking something. Any input here is greatly appreciated.
One last thing - the feed rate reflected in the “Status Reports” portion of the “Makerverse” GUI did show the desired feed rates in both experiments.