SKR Pro Freezing in Marlin

I had something happen during a carve this evening that’s never happened to me before. Three hours into my carve, the machine froze up.

I am running a Primo with an SKR board and TFT from the V1 store, and I used ESTLCam for my toolpath creation. My typical process is as follows:

  • Save gcode file from ESTLCam to SD card
  • Insert SD into TFT
  • Move tool manually (with TFT controls, no end stops) to origin position
  • Press reset button to create new origin coordinates
  • Use TFT controls to jog each axis once in each direction to engage steppers and return to origin.
  • Turn on router (flip the switch)
  • Hold TFT knob to switch to Marlin mode
  • Start cut/carve

I have had troubles in the past with freezes when staying in TFT mode, but ever since I started using Marlin mode I haven’t had a single issue until tonight.

I guess my question(s) is/are…

  • What are some of the potential reasons for this? Nothing was disconnected, because when I reset the machine to remove the ruined piece, all of the steppers jogged appropriately.
  • Is there any way to go through a gcode to figure out where it stopped. Either to see if there is an issue or if there is a chance to restart where it messed up.
  • is there any way to unfreeze when this happens?

As a side note, in the past I’ve recovered from v-carve mess-ups by setting my carve sequence in ESTLCam to “as created.” This lets me create a new carve program with just the remaining features and finish the project. I forgot to do that this time.

That sucks the job failed. Carves can be very difficult to get restarted due to alignment. I offer this based on shared failure experience realizing you lost the piece already. It is frustrating and demoralizing sometimes when this happens. Yours could be a gcode fault or a memory error or a power glitch from s failing power supply or a loose wire. My failures have been typically my fault from motor skips from external debris or too much foam on the rails or a cable chain attachment gone wrong causing something to bind (mpcnc-major reason an LR4 sits in its place).

When jobs stop part way, I usually do the following:

  1. Determine where it stopped generally
  2. Use a gcode visualizer to find the exact line.
  3. Cut everything except the gcode startup before this line. Sometimes i keep a few lines in to verify the position is correct such as z height.
  4. Restart job with the edited file

In order for this to work, for each job before beginning, i typically home or define home in a location where a hole can be drilled with the cutting tool so it can be relocated after a power cycle. Then once zeroed i drill a hole. Another way to do that is run the homing command then set your machine position manually, record the offset numbers for each axis, then in the marlin menu, then use the v1 menu to zero x and y. In klipper i have a macro key to zero xand y.

1 Like