Software crashes while jogging Z axis using UI knob

Like the title says, I finished assembling the printer yesterday and while moving Z axis using the knob on the control panel, the software crashes/resets, disabling all functionality. It freezes or resets itself fully.

Swapped the drv8825 pwb with the X axis, but the problem is prone to the Z.

Using repetier works fine. anyone else noticed the same? Flipping Z down might be handy for servicing the hotend. I was planning on using it stand-allone, so this is a tad annoying.

Another issues is that the NTC’s wires (hotend) have way too much tin on them, causing the isolation to be damaged while bending it gently in the hotend. As a result the 100k ntc had a short to at one side… (solved it by turning around the thermistor, but it looks like crap now… :slight_smile:

It’s a known bug with Marlin.

[quote]VEL327 wrote:
The problem when you move the Z axis down and then the controller resets or freezes is known. This is a marlin bug. We have submitted the bug to the marlin developers. The bug is also present in the other marlin based printers (ultimaker 1, K8200, …) The workaround at the moment is to slowly move the encoder when lowering the Z axis and not turn fast to the point you want the axis to go. If you turn the encoder slowly and you let the buildplatform catch up then the controller doesn’t freeze or reset. When we have a solution a firmware update will be released.[/quote]

Quote taken from this thread: viewtopic.php?f=62&t=13254

Best regards

Thank you!!

With the latest firmware it is a lot less but still present. But I haven’t heard back from the marlin guys yet.

@VEL327

I have also some Arduino experience and I wouldn’t mind to look at it since I also have that problem.
Do you know something more about that bug?

Cheers,
Dylan

We know it’s a bug that exists on all marlin installs but the behavior changes with the amount of steps per unit, acceleration values and so on…

Ooh then it isn’t so easy to fix it if you don’t wrote/know the code…

Cheers,
Dylan

Isn’t it a time-out that’s causing the problem? since the Z is relative slow, and the screen resets to default settings very soon… Perhaps the ‘reset to default’ screen can be set longer.