Belts appear to get tighter as a long print progresses leading to warning

I have noticed the belts appear to get tighter as a print progress, I have particularly noticed it when I am doing multiple depth cuts in a long print. In the attached file I got a current exceeded warning and belts were very tight. I stopped the cut, manually deleted the lines up to where it had stopped, leaving the setup codes at the beginning and successfully completed the cut. Any ideas welcome.

[MSG:WARN: Motor current on Bottom Right axis exceeded threshold of 4000]
Stop Maslow and Gcode
Stop Maslow and Gcode

Maslow-serial - 2026-02-13T162358.535.log (3.8 KB)

1 Like

If you do a ā€œretract allā€ after that happens what do the offsets look like?

That would tell us if the belt is losing position

I’ll set it up and give it a go. I had also Released Tension and Applied Tension, before restarting. The print did restart in the right place, so I don’t think it had lost position.

1 Like

I let run even after the warning. It finished the file, but then i couldn’t get it release tension until I powered off the Maslow and restarted. Then it came back unknown so I did the retract extend dance. Readings were meaningless.

1 Like

All of those things seem like valuable and significant evidence about what is going on, but what exactly all the evidence is pointing to is a mystery to me.

Off the top of my head there are only two things which could be going on which lead to the tension going up over time.

  1. The encoder is losing position somehow. That could be either a software or hardware thing, but the way to identify it would be to get a retract all which shows a significant offset at the end

  2. The z-axis position is drifting. Because we compensate for the z-axis height when computing the belt lengths if the z-axis position is changing somehow that would lead to a change in belt tension.

The z-axis is a little tougher to diagnose because it is stepper motor driven so we don’t have any feedback on where it really is other than looking at it by hand.

If you look on the ā€œFluidNCā€ tab you can see the ā€œZmā€ readout which is the z-machine value which is the z-axis position independent of where the z-home is set. That value should match up with the real world measurement between the top of the stepper motor and the bottom of the router clamp, or if the router clamp is lowered all the way down it should read 0.

I think it time it might be useful to echo Zm in the Maslow display (maybe as something like ā€˜Zabsolute’?).

For validating Z - there’s a spare input that can be used for touch probes isn’t there? Could that be used for a limit switch as well (I should be able to fit a limit switch in the 1.1 version of the MonolithMaslow)?

If not Z missing steps - there’s no offsets or anything that can change over time that could be accumulating rounding errors or similar is there?

1 Like

I have been thinking that too. I will follow that up.

2 Likes

Done Display machine Z position (Zm) alongside work position on tablet interface #778 (#777)
index.html.gz (132.2 KB)
firmware.bin (1.9 MB)

2 Likes

@BarbourSmith This one also displays Xm and Ym coordinates in addition to Ym, useful if trying to get a consistent position independent of where home is set, or setting home on a easily replicable basis. I know you can get it from the Control menu, but that is not convenient.


index.html.gz (132.6 KB)
firmware.bin (1.9 MB)

1 Like

Having the Xm and Ym visible shows micro adjustments to sled position when Z is moved. The sled moves (order of 0,02mm) when Z raised or lowered.

1 Like

Bar wrote:

  1. The z-axis position is drifting. Because we compensate for the z-axis
    height when computing the belt lengths if the z-axis position is changing
    somehow that would lead to a change in belt tension.

note that the Z axis is far more likely to skip steps when raising (fighting
gravity and belt tension) than when lowering.

tension would only be increasing if the Z height is higher than it thinks it is.

possible (and worth checking on), but doesn’t seem likely

David Lang

1 Like