Untimely stop and reversal of movement, SZP sensor reading error
-
Hello everyone,
I have some little problems with my motherboard, a 3 mini 5+ Ethernet.
My very first problem came this morning. I had already launched last night, a long print, which worked very well, but this morning my printer was switched on, except that it was in its initiation state, with no print status, all the heating elements were cold, and no gcode line backup... (After checking, no power failure at home)
I restarted another print. After a few hours, the printer stopped and also without any backup (although it was well configured in config.g and in any case there was no power failure whatsoever).
On the spot, I tried to execute a "resurrection" but my Y axis vibrated instead of moving, even though the nozzle wasn't blocked by the print.
I took a closer look at my power supply, but it turned out to be stable and functional.
I restarted my machine again with a Y axis that reversed direction...
Another attempt, and again vibrations, with no movement of the Y axis.
I have a mini 2 extension card, and I was able to try the same motor on other drivers. It worked perfectly.Now for some additional information: on cura as on others, I've set a motion resolution of 0.05mm at a speed of 60mm/s. Can these interruptions be due to processor overload? Could these interruptions be due to processor overload? With an even lower resolution I had jerky movements but no lag whatsoever and a functional impression.
Then, on my mini 2 card, none of the drivers are working now. Should I buy another one, or will the problem come from the main card?Second question:
When I scan with the SZP on my last scan line, I get an error telling me that the points have been skipped, and of course telling me the coordinates. Having scanned 400 points, I tried to reduce the mesh size by using a 25 mm square spacing. I tried to reduce the scanning speed to a very slow speed, but still obtained the same error. However, the scan on the rest of the board works fine with your correct data. I've tried to update everything again, but without success. What could be the cause?Thank you in advance for any answers you may be able to give me.
Translated with deepl.
-
@Esteban said in Untimely stop and reversal of movement, SZP sensor reading error:
I get an error telling me that the points have been skipped
This means your grid has points that are outside of the reachable area of the probe. When choosing the grid extents, take into account any offset your probe has.
For the problem of prints failing, can you gather a diagnostics report using M122 right after it happens?
For the problem with drivers, it's not totally clear what the issue is. Are you saying that motors connected to the mini2 card, don't work?
In general I think it would be beneficial to split up your issues into individual forum posts. It's much easier to tackle one thing at a time.
Also please share your config.g and the results of M122 here so we have a better idea of what you're working with.
-
@Esteban any time you get an unexpected reset of the Duet, run M122. The resulting report includes the reason for the last reset, and more detail if it was a software reset.
-
Okay, so accessibility depends jointly on the G31 and M208 command?
Concerning my M122, I'm afraid I won't be able to run it after a print stop, because my drivers aren't working due to the failure...
But when I run it on unload, this is what I get, along with my configuration :
