Version 1.04 Home position not consistent and Release Tension: Unknown State

Software
1

1.
Home not working as expected. Set home, did test print and clicked on Home symbol to get back. M4 did not move. Moved M4 using jog to get to new home position, Saved new home, Jogged up then selected Home symbol and M$ went to old home position, so I did the following to test and duplicate the problem.

JogTo: '$J=G91F2500X-100Y-100
’
JogTo: '$J=G91F2500X-100Y-100 Jogged to this position then set XY Home
’
Home pos set for: X
Home pos set for: Y
JogTo: '$J=G91F2500X0.06Y-99.95 Clicked on home symbol and M4 moved down
’
JogTo: '$J=G91F2500X0.06Y-95.99 Clicked on home symbol and M4 moved down
’
JogTo: '$J=G91F2500Y100 *Jogged to this position then set XY Home again
’
Home pos set for: X
Home pos set for: Y
JogTo: '$J=G91F2500X0Y0 Clicked on home symbol and M4 NOT move
’
JogTo: '$J=G91F2500Y100 **Jogged up 100 mm **
’
JogTo: '$J=G91F2500X0Y-3.64 Clicked on home symbol and M4 moved down
’
JogTo: '$J=G91F2500X0Y-96.91 Clicked on home symbol and M4 moved down
’
JogTo: '$J=G91F2500X0Y-92.5 Clicked on home symbol and M4 moved down
’
JogTo: '$J=G91F2500X0Y4.23 Clicked on home symbol and M4 moved up
’
JogTo: '$J=G91F2500X0Y89.7 Clicked on home symbol and M4 moved up
’

2.
Release Tension goes to an Unknown State, and it initially only released tension on TR/BL. After 3 goes it finally Released tension on TL/BR.
Release Tension
[MSG:INFO: Requesting state change from Ready To Cut to Releasing Tension]
[MSG:INFO: Requesting state change from Releasing Tension to Unknown]
Release Tension
[MSG:INFO: Requesting state change from Unknown to Releasing Tension]
[MSG:INFO: Requesting state change from Releasing Tension to Unknown]
Release Tension
[MSG:INFO: Requesting state change from Unknown to Releasing Tension]
[MSG:INFO: Requesting state change from Releasing Tension to Unknown]
Release Tension
[MSG:INFO: Requesting state change from Unknown to Releasing Tension]
[MSG:INFO: Requesting state change from Releasing Tension to Unknown]
Apply Tension
[MSG:INFO: Requesting state change from Unknown to Taking Slack]
[MSG:INFO: Cannot take slack until the belts have been extended]
Stop Maslow and Gcode

2

Does Release Tension only release 2 belts?
Is it possible to set it to release all belts by a known amount?
Can M4 be made to “remember” its X/Y position so a subsequent Taking Slack command will take up the same amount of belt to get back to the same position?

3

Ian Abbott wrote:

Does Release Tension only release 2 belts?

are you set to vertical or horizontal mode? I would not be surprised if vertical
only moved the lower belts.

David Lang

4

Vertical

5

Ian Abbott wrote:

Vertical

when you are vertical, the top belts will always be under tension (due to
gravity) so it would make sense to only spool out from the bottom belts.

David Lang

6

Problem I had was belts TL and BR did not release, which makes it really hard to take belt off anchor. TR/BL was fine, plenty of slack there.

1 Like
7

It should release all four, but the way it works is that it makes the belts compliant (the same way they are when you are extending them) for 0.5 seconds. It’s possible that maybe something was just right so that those two didn’t extend.

Does it happen every time?

The home jog position is a little bit funky in that it calculates the distance to the home position and then commands a jog of that distance, but it needs the machine to be stopped to calculate it right. If the machine is still moving it might give you strange behavior.

8

No, I managed to loosen them after 3 attempts of release tension. Each time the 2 belts which were already loose let out more. Would it be better to only release the lower belts BR & BL, then Take slack could pull them tight again, potentially restoring to a known position (M4 knowing where it is). Might need a new command to different from Take Slack, like Restore Position).

Machine was not moving when I clicked home and I had not seen this with previous versions.
Thanks for your support. I don’t know how you keep it up.

1 Like
9

I’ll give this a test and see if I can replicate it, maybe we introduced a new bug. Thanks for the heads up!