M4 Calibration seems good, but jogging literally does nothing

Troubleshooting
1

I’ve got my M4 assembled, up on the frame, and run it through it’s first calibration, which it passed (so it tells me).

But when I try jogging it anywhere, the fan spins up, but none of the motors do, it doesn’t move at all.

However, Z axis moves do work.

I’m running 0.72.1

Where do I start diagnosing what’s wrong?

2

Ahh, silly me.

New machine, new workflow

I had turned the M4 off, therefore it forgot where it is, so when I turned it back on and told it where to go, it told me “I’m sorry I can’t do that Dave”

Did a “Release Tension”, unmounted the M4, “Retract All”, “Extend All”, remounted, “Get Tense Again”, and now it knows where it is.

4 Likes
3

Did you get any error messages when you tried to move? I want to document the symptoms in the troubleshooting section of the wiki.

2 Likes
4

I really hope Bar or I get to this soon :slight_smile: has bitten me more than once too!

2 Likes
5

I got saving to non-volitle memory working in last week’s update so the groundwork is there. I think that the hard part is going to be figuring out exactly what the user experience looks like and how we make sure that we communicate well when the machine loads it’s position and when it doesn’t.

Maybe it should be an opt in thing? Like instead of pressing extend all you can press “Load Position”?

1 Like
6

Bar wrote:

I got saving to non-volitle memory working in last week’s update so the
groundwork is there. I think that the hard part is going to be figuring out
exactly what the user experience looks like and how we make sure that we
communicate well when the machine loads it’s position and when it doesn’t.

Maybe it should be an opt in thing? Like instead of pressing extend all you
can press “Load Position”?

That works, make sure that there is some way to detect that power was cut while
moving (similar to the earlier maslow, save position after a couple seconds of
being idle and then clear this before starting to move)

I think there should be separate load belt position vs load Z position, the Z is
much more likely to change as the machine is handled

David Lang

2 Likes
7

No error messages at all - they really would have helped.

To make matters worse the UI shows the respective X Y position as changing

1 Like
8

Agree. this might be something we can look into. if the maslow does not know where it is it should message the UI that and we should pop a dialog to do the “re-hang” dance… Also it should not move in the fluid code, causing the coordinates to change…

1 Like