I have tried two cuts with the new maslow 4.1 both just stopped ... Help

Troubleshooting
1

I have tried two cuts with the new Maslow 4.1 both just stopped very far in. The last was gcode from the Garden the standing desk. The unit just stopped and had to be reset. I do not know what to do, at least got the serial data this time. Could I have done something to recover from this?

Here is the serial data:

Serial Messages
Index.html Version: 1.12
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v3.0.x (noGit)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 5]
[MSG:INFO: Axis A (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.110]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.110]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:Legend Wifi_EXT24]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.68.103]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/\]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Channel auto report interval set to 50 ms]
Retract All
[MSG:INFO: Retracting all belts]
[MSG:INFO: Requesting state change from Unknown to Retracting Belts]
[MSG:INFO: Succeeded]
[MSG:INFO: Bottom Left pulled tight with offset -0.150]
[MSG:INFO: Top Right pulled tight with offset -0.021]
[MSG:INFO: Top Left pulled tight with offset -0.054]
[MSG:INFO: Bottom Right pulled tight with offset -0.150]
[MSG:INFO: Requesting state change from Retracting Belts to Belts Retracted]
[MSG:INFO: Succeeded]
Extend All
[MSG:INFO: Extending all belts]
[MSG:INFO: Requesting state change from Belts Retracted to Extending Belts]
[MSG:INFO: Center coordinates updated in MaslowKinematics: X=2141.328 Y=1586.945]
[MSG:INFO: Succeeded]
[MSG:INFO: All belts extended to 2570.000mm]
[MSG:INFO: Requesting state change from Extending Belts to Belts Extended]
[MSG:INFO: Succeeded]
Apply Tension
[MSG:INFO: Requesting state change from Belts Extended to Taking Slack]
[MSG:INFO: Succeeded]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.000 TR: 0.000 BL: 2.489 BR: 3.115]
[MSG:INFO: Center point deviation within 12.000mm, your coordinate system is accurate]
[MSG:INFO: Current machine position loaded as X: 29.003 Y: 33.029]
[MSG:INFO: Before update - mpos: X=nan Y=nan Z=32.000]
[MSG:INFO: Setting motor positions directly from measurements:]
[MSG:INFO: TL belt: 2462.917 TR belt: 2556.718]
[MSG:INFO: BL belt: 2557.571 BR belt: 2505.668]
[MSG:INFO: After update - mpos: X=28.617 Y=35.085 Z=32.000]
[MSG:INFO: Requesting state change from Taking Slack to Ready To Cut]
[MSG:INFO: Succeeded]
[MSG:INFO: Tool No: 2]
[MSG:INFO: Using spindle NoSpindle]
[MSG:ERR: 20 (Unsupported GCode command) in /sd/Desk_Complete.nc at line 4]
[MSG:WARN: Position error on Bottom Left axis exceeded 15mm while running. Error is -64.470mm Counter: 1]
[MSG:WARN: Previous error was -64.470mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.020mm Counter: 1]
[MSG:WARN: Previous error was 15.020mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.027mm Counter: 1]
[MSG:WARN: Previous error was 15.027mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.065mm Counter: 2]
[MSG:WARN: Previous error was 15.065mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.023mm Counter: 1]
[MSG:WARN: Previous error was 15.023mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.073mm Counter: 2]
[MSG:WARN: Previous error was 15.073mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.111mm Counter: 3]
[MSG:WARN: Previous error was 15.111mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.007mm Counter: 4]
[MSG:WARN: Previous error was 15.007mm]

2

Can you copy the Desk_Complete.nc file to here.
If you set the home position and haven’t changed it, it should be possible to manually edit the Desk_Complete.nc file to skip over the completed part and resume where it failed. You will have to work out exactly where it failed. I use a program called CAMotics (https://camotics.org/) to simulate a cut on the computer (no connection to Maslow hardware), and it lets you run through the cut and makes it easier to find where it stopped.

1 Like
3

Kevin Davis wrote:

[MSG:WARN: Position error on Bottom Left axis exceeded 15mm while running. Error is -64.470mm Counter: 1]
[MSG:WARN: Previous error was -64.470mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.020mm Counter: 1]
[MSG:WARN: Previous error was 15.020mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.027mm Counter: 1]
[MSG:WARN: Previous error was 15.027mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.065mm Counter: 2]
[MSG:WARN: Previous error was 15.065mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.023mm Counter: 1]
[MSG:WARN: Previous error was 15.023mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.073mm Counter: 2]
[MSG:WARN: Previous error was 15.073mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.111mm Counter: 3]
[MSG:WARN: Previous error was 15.111mm]
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.007mm Counter: 4]
[MSG:WARN: Previous error was 15.007mm]

This is saying that the bottom right arm was not moving correctly or your
calibration was way off.

was the belt slack when it ran into grief? what direction was it trying to move?

David Lang

1 Like
4

Desk_Complete.nc (262.3 KB)

Here is it.

5

I think may have been obstructed. I have since removed the object.
Do I need to rerun the calibration before retrying or should it be fine as long as the obstruction is gone?

Kevin Davis

6

Was the obstruction there when you ran the last calibration? If it was yes. How far did the cut go before it failed? You could also try running it without a bit in the router to see if it fails again.

7

It was not there at the last calibration. I am going to recalibrate anyway to be safe.

Also, the cut went until the obstruction diverted the Maslow, I did not notice it until I went back and looked at the cut. It actually pulled the machine off by at least an inch.

Thank you for your help.

Kevin

8

OK, suggest you have a look at the CAMotics program, I find it useful to get an idea of how its going to cut.

9

I plan to use it on the next cut.

10

Sorry to jump on this, but I think I have the same issue but nothing is blocking or obstructing the maslow unit.

I have increased my calibration size from 400x400 to 1200x600, grid is now 9x9 and the pull force is up to 1300. It took a little while but I was getting fitness values over 2.

When the unit travels to the far right hand side of the cutting area it emergency stops stating the position is out.

I’ve checked the heat map and its actually stopping in an area that is highlighting as green.

I’ve noticed that one of my cables isn’t reeling in or pulling tight.

I’ve also noticed that my stepper motors are no longer moving but I’ve already changed the board maybe these two things are linked? @bar

My next move was to strip it down and see if they are starting to bind at the bottom or if my steppers are broken either way I’m feeling pretty frustrated agh!

20251022_121220
20251022_1212201560×4000 1.76 MB

20251022_121349
20251022_1213491920×749 89.2 KB

20251022_121011
20251022_1210111560×4000 1.46 MB

11

This sounds like a calibration issue to me. Someone else had this same issue last week which prompted us to start working on how to automatically calculate the best calibration grid size for a given frame so you don’t have to.

Can you try running the find anchor point locations process with a larger grid (something like 500x900mm)?

Basically what’s happening is that since the process didn’t use any information from the far right side of the sheet when finding the anchor locations they aren’t quite correct over there.

12

Ive tried a 600 x 1200 should I try an even larger area?

13

stebaker125 wrote:

Ive tried a 600 x 1200 should I try an even larger area?

what is your frame size?

the larger the area of the calibration grid the better, unless you get to a
point where the arms hit the uprights on the sled)

David Lang