Calibration question (1 smaller broken belt)

oops… my pictures didn’t come through when I commented last using my phone. Here are pictures of my width and height:


I am entering width of 2036mm and height of 1334.3mm in the software.

Here are the measurements of my frame on the angle:


I guess technically it is slightly racked, but only off by 8 or 9mm. That should be close enough right?

I got through the 3x3 calibration once with the current frame setup by using:

Machine width: 2036
Machine height: 1345 (larger than the measured height)

Calibration width: 500
Calibration height: 300

It got through the 3x3 calibration with a .48 fitness, but after the 5x5 calibration it returned a .16 fitness.

I spent lots of time trying different measurements with no luck. I ended up going back and trying the calibration again with the same settings (2036 x 1345) and instantly got the emergency stop after the 1st waypoint.

I will take a look at the onshape doc and keep plugging away at trying various other measurements.

Thanks guys!

it’s important to keep in mind that all calibration is doing is finding the
coordinates for the anchors, any way to do that will work.

David Lang

1 Like

Reading through the thread, I was wondering if you were confusing workpiece dimensions with frame (anchor to anchor) dimensions, but seeing your measurement pictures, that’s not it.

I’m wondering about the push-to-extend bug.

You might try increasing the increment you are adding to/subtracting your frame size. 1 mm is awfully small. Try something more like 20mm.I did not encounter this problem with my setup, so I’m not speaking from experience here, though. Someone correct me if I’m wrong.

1 Like

If you can capture the output (save serial) and post it we can play with it in the calculator

When I took your original post’s CLBM line into https://m4cal.etskinner.com/ and gave it a 9999x9999 frame size (in other words just have it guess the anchors) it came up with these locations for the anchor points:

Calibration values:
Fitness: 0.23101162949504736
Maslow_tlX: 8.3
Maslow_tlY: 1727.3
Maslow_trX: 1722.3
Maslow_trY: 1733.4
Maslow_blX: 0.0
Maslow_blY: 0.0
Maslow_brX: 1747.3
Maslow_brY: 0.0
1 Like

Absolutely! Here is the latest attempt from a few minutes ago. I was about to start playing with the online tools as well:

Serial Messages
[MSG:INFO: Channel auto report interval set to 50 ms]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: FluidNC v0.76 (Maslow-Main-67a72cf4-dirty)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Config messages ran]
[MSG:INFO: Axis Y (-1219.200,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: Kinematic system: Cartesian]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:Smyk]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: No SSID]
[MSG:INFO: AP SSID maslow IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: Caution: Unlocked]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Top Right pulled tight with offset -1028.732]
[MSG:INFO: Top Left pulled tight with offset -1050.773]
[MSG:INFO: Bottom Right pulled tight with offset -1093.406]
[MSG:INFO: Bottom Left pulled tight with offset -1105.516]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.183 TR: 0.190 BL: 1.328 BR: 2.989]
[MSG:INFO: Center point deviation: TL: 0.183 TR: 0.190 BL: 1.328 BR: 2.989]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
[MSG:INFO: Zeroing z-axis position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.055 TR: 0.056 BL: 1.258 BR: 4.127]
[MSG:INFO: Measured waypoint 1]
[MSG:INFO: Measured waypoint 2]
[MSG:ERR: Unable to move safely, stopping calibration]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
[MSG:ERR: Unable to move safely, stopping calibration]

Just as an experiment (not sure this will work at all) Could you try entering in 1725 x 1725 for your frame size and then see if it can jog (just set the values, save, then reboot and do the retract extend, hang, apply tension) then see if it can jog at all? If it does, then I’d try a calibration with those numbers and see if it gets further.

2 Likes

also, maybe set the frame size to something very large and do retract / extend and just pull the belts out as far as possible (don’t go too far or they start spooling the wrong way – don’t ask me how I know :slight_smile: ) , then retract all again and make sure they are properly spooled on?

1 Like

Good suggestion, but the 1725 x 1725 frame size didn’t make a difference. Still failed after waypoint 2

I tried this to the best of my abilities with 1 broken belt, and all belts look like they are sitting properly.

I made a javascript version of the manual calibration to replace that onshape doc, it’s ~5k (but can be minified and compressed down to ~1k)

http://lang.hm/maslow/maslow4_manual_calibration_simple.html

1 Like

Thanks for that. I’ll enter the values from there and try things out. Unfortunately I am just leaving town, so I won’t know how things will work out until next week.

Paul Smyk wrote:

Thanks for that. I’ll enter the values from there and try things out.
Unfortunately I am just leaving town, so I won’t know how things will work out
until next week.

not a rush. this is theoretical work, we haven’t had people test it and see how
well it works yet. But since you are having problems with the automated
calibration, this may get you something close enough to move on to real work :slight_smile:

David Lang

Darn, well I am stumped. Maybe a video of the calibration when you get back will help if you can

2 Likes

After everyone’s help and advise, I have managed a successful calibration! With a fitness level of 1.17 to boot!

I am very embarrassed to admit my mistake, but I can handle the abuse :crazy_face: I turned my maslow 90 degrees at some point without realizing it and was trying to run calibration vertically instead of horizontally.

The frustration trying to figure this all out taught me alot about the machine.

Thanks again for everyone’s help.

1 Like

great to hear (and I think that’s the highest fitness I’ve seen), could you do a
summary post detailing your frame, etc to make it easy for others to get a ‘this
works’ summary?

David Lang

1 Like

Yup. Coming soon in a separate post. It’s a very different over the top build.

2 Likes