my 4.1 keeps crashing mid cut and or even before i get it all the way ready to cut again after the last crash
1 Like
What are the symptoms of it crashing?
it stops cutting and disconnects me then restarts and makes me retract and extend again before it moves again
1 Like
That does sounds like the ESP32 is crashing.
Is this on a 4.0 or 4.1? It could be a lose connection somewhere.
Is there any information in the log file which might tell us something?
Do you by any chance have debug mode running which shows how much power each motor is drawing? I’ve seen that cause issues
4.1, which log? and where would i find it? and i do not how do i turn it on?
You can use this button here after a crash:
It will tell us everything which happened with the machine which should help to find the issue.
If you did not turn it on then it is off. Do not worry about that.
Maslow-serial.log (3.4 KB)
1 Like
This log looks totally normal, but it just shows the machine powering up.
Can you capture the log right after the machine crashes? That should show us what is going wrong.
it restarts when it crashes thats the first log i can get when it restarts, i will try and save it on the computer that its running off of tho to try and get it as fresh as possible
1 Like
When the machine restarts the log should stay on the computer that it is running off. I believe that there is even a popup when the machine disconnects which will ask if you want to save the log for exactly this kind of situation.
It makes it much easier to diagnose what is going on.
1 Like
alright good to know, thank you, i will try and run it again if it crashes ill put the log here
Maslow-serial (6).log (3.0 KB) may have crashed, during retraction of the belts, came back to laptop and it was disconnected
1 Like
Maslow-serial (7).log (2.8 KB) just barely got half way into extending one belt and it stopped because it crashed
1 Like
Hmm that is strange. Nothing in either of those files shows anything being out of the ordinary.
Can you try deleting your maslow.yaml file and replacing it with a new one? Maybe there is something weird going on with the math settings that is giving it a divide by zero error or something like that.
I would also try unplugging and re-plugging all wires into the control board just to make sure that nothing is lose which can cause weird behavior
is there any info that i need to save from the maslow.yaml file for a new one?
1 Like
Saving the whole file isn’t a bad idea.
Do you feel good about your anchor point locations? If yes then you want to save that info. You can find it by clicking on FluidNC and then Config Items
And scrolling down to this bit here:
1 Like
how do i know if they are good locations? it was cutting good when it wasn’t crashing? also how are the anchor point locations determined? just the calibration/finding anchor points?
also after replacing the maslow.yaml file and replacing the anchor points will i need to recalibrate or am i doing that by replacing the anchor point locations in the new file?
If it’s cutting good then you know they are good 
Exactly. The find anchor points process will locate them for you.
You will not need to re-calibrate. That is exactly what we’re doing by copying them over.
1 Like
thank you really appreciate the assistance
1 Like