My "2 Wifi" is un-baby-stepping

dc42

Can you try with the 2.03beta2 release?

gnydick

@dc42 I'm not going to put anything but stable releases on. I have too many prints to go out to worry about new bugs.

gnydick

I'm really having a hard time getting any prints done. I really need a solution. Also, I don't know if it happens this way always, but I noticed it "un-babysteps" during a travel.

dc42

I'm sorry, it it's fixed in the current beta then as far as I am concerned, it is fixed. I don't have time to investigate possible problems in multiple firmware versions when just one user is affected. There were major changes to the babystepping code in 2.03 as a result of other changes, which resulted in the babystepping code being significantly simplified. So it wouldn't be just a case of back-porting a bug fix.

I have had only one bug reported in 2.03beta2, which is that if you use the M575 "Probe Tool" command then custom endstop numbers don't work. You can see the feedback from users in the 2.03beta2 thread.

gnydick

@dc42 so you're saying you did confirm the issue? Or, are you saying that you can't reproduce it in the 2.03beta2?

dc42

@gnydick said in My "2 Wifi" is un-baby-stepping:

@dc42 so you're saying you did confirm the issue? Or, are you saying that you can't reproduce it in the 2.03beta2?

I'm saying that I can't reproduce it in 2.03beta, also that there have been code changes made that could mean that 2.03beta behaves differently form 2.02.

gnydick

@dc42 well I tried the latest beta, it's still happening. Is there any debug mode I can do for you? Maybe hooked up to the serial terminal?

Phaedrux

Were you able to figure out of your motors were cooked? Did you try any of the other suggestions above?

dc42

@gnydick said in My "2 Wifi" is un-baby-stepping:

@dc42 well I tried the latest beta, it's still happening. Is there any debug mode I can do for you? Maybe hooked up to the serial terminal?

That's odd, I took your config.g file, made minimal changes to allow it to work on my bench system, and i was unable to reproduce the problem.

Does the un-babystepping fail only in one direction; for example, if your machine has a lifting bed, does baby stepping to low the bed always succeed and lifting it sometimes fail?

gnydick

@dc42 IIRC, it fails in both directions. Sometimes it's a slow winding back to where it was, other times it's the complete sum of baby steps e.g. if I click it 5 times and it moves .05 x 5times, then it will undo it .25 all at once.

Phaedrux

Are you by chance baby stepping below your M208 Z axis minima?

gnydick

Well, yeah, that's kinda assumed to be one of the use cases for baby stepping. But it's not always the case.

wilriker

@gnydick AFAIR baby stepping honors axis minima (and maxima). But it should never even try and later undo it so that should not be the source of this issue.

Phaedrux

Reason I ask is because I just had baby stepping kind of freak out on me, but not exactly how you were describing. I was trying to lower it quite a bit, (-0.3ish) and it started to throw G1/G2/G3 errors something about moving outside machine limits and the XY movement would kind of reverse. It was doing the skirt at the time. When it started moving unexpectedly I killed the power and lost the error messages.

gnydick

@phaedrux I've seen those too. Sometimes the board actually locks up or reboots the web host portion.

gnydick

@dc42 OK, Now I saw it happen with a regular move, no print was happening, I was just calibrating Z.

I homed it, moved my head to the center of the bed, brought it to zero. Then I +.5 to see if the head dropped at all (indicating that the bed was pushing up on the head) and it wasn't pushing on the bed, so I -.5 and the bed came back up to meet the nozzle, and then it, all on it's own, the bed moved back down +.5.

I CAN'T be the only one experiencing this on multiple revisions of firmware. And I'm pretty sure I saw it on my Maestro too.

This has to be looked at. I'm not very happy that you just kinda ignore it because you think I'm the only one experiencing it. To be totally honest, I'm not your average person. I tinker with things, explore all of the ins and outs, as well as am more observant than 99.999999999% of people. It's a curse. In my career, I'm constantly pointing out things that are broken that nobody has seen, sometimes for decades.

You can take it from me, if I say something is broken, it's broken.

Now, I'll ask again, is there any debugging help I can provide?

gnydick

I have a possibly interesting update....

One of my Z motors was apparently dying. It finally died today. Is it possible that a faulty motor in a 2 motor series could cause this behavior?

Phaedrux

@phaedrux said in My "2 Wifi" is un-baby-stepping:

Were you able to figure out of your motors were cooked? Did you try any of the other suggestions above?

I guess that answers that?

dc42

@gnydick said in My "2 Wifi" is un-baby-stepping:

I have a possibly interesting update....

One of my Z motors was apparently dying. It finally died today. Is it possible that a faulty motor in a 2 motor series could cause this behavior?

It's unusual for stepper motors to die. In what way did it die: an open circuit coil, or something else?

If a coil of one Z stepper goes open circuit, then power to the series-connected coil of the other stepper motor will be cut too. When this happens, it is quite possible that commands to move the bed up will move it down instead. Whether it does that or just vibrates will depend on the weight of the bed and other factors.

When you have replaced the faulty stepper motor, let us know whether you are still having this un-babystepping problem.

gnydick

@dc42 oh well, I replaced the motor and it's still happening.
I'm not sure how it died. I think it's bearings though. It was really hard to turn the motor by hand while it was disconnected, and made a soft grinding sound.