Are you still getting this error message?
I’m hoping to have a version out next week which will eliminate that error message entirely as an option by recomputing it automatically
Are you still getting this error message?
I’m hoping to have a version out next week which will eliminate that error message entirely as an option by recomputing it automatically
My last run yielded these numbers:
[MSG:INFO: Center point deviation: TL: 0.284 TR: 0.119 BL: 37.354 BR: -58.277]
[MSG:INFO: Measured waypoint 1]
[MSG:INFO: Measured waypoint 2]
[MSG:ERR: Unable to move safely, stopping calibration]
Interesting. That’s a different error message. That one means that the math is producing some impossible result (like that to move to the left the belts on the left side of the machine need to get longer). There’s for sure something funky going on with the machine’s understanding of the world, but I’m not sure exactly what it is.
Does any of this depend on the smoothness of the material to be cut?
Bar wrote:
There’s for sure something
funky going on with the machine’s understanding of the world, but I’m not sure
exactly what it is.
can we enhance this error message to report the state of the machine so that we
can see what it thinks is wrong better?
David Lang
It shouldn’t depend on the smoothness of the material as long as it’s not so rough that its having a hard time sliding.
Can you try uploading your maslow.yaml file here? That will let us see all your machine settings. You can download a copy by clicking this little download button here:
@dlang this error message is only caused the machine needing to move in a direction, while the math tells us that the belts need to get longer for that to happen. In this case since it was trying to move from point 2 to 3 we know it couldn’t find a valid solution to move in the up direction.
Johnnie Eskue wrote:
Does any of this depend on the smoothness of the material to be cut?
it should not.
David Lang
Bar wrote:
@dlang this error message is only caused the machine needing to move in a
direction, while the math tells us that the belts need to get longer for that
to happen. In this case since it was trying to move from point 2 to 3 we know
it couldn’t find a valid solution to move in the up direction.
but what were the belt lengths and anchor points that it was working with, etc?
how is it that it can’t find a valid solution here?
David Lang
This will tell us
OK, got it. Is a bit cold for me in my shop today, but here it is - maslow.yaml
board: Maslow
name: Maslow S3 Board
meta:
Maslow_vertical: false
maslow_calibration_grid_width_mm_X: 2000.000000
maslow_calibration_grid_height_mm_Y: 1000.000000
maslow_calibration_grid_size: 9
Maslow_tlX: 0.000000
Maslow_tlY: 2300.000000
Maslow_trX: 2940.000000
Maslow_trY: 2300.000000
Maslow_blX: 0.000000
Maslow_blY: 0.000000
Maslow_brX: 2940.000000
Maslow_brY: 0.000000
Maslow_tlZ: 100.000000
Maslow_trZ: 56.000000
Maslow_blZ: 34.000000
Maslow_brZ: 78.000000
Maslow_Retract_Current_Threshold: 1500
Maslow_Calibration_Current_Threshold: 1500
Maslow_Acceptable_Calibration_Threshold: 0.450000
stepping:
engine: Timed
idle_ms: 240
pulse_us: 4
dir_delay_us: 0
disable_delay_us: 0
segments: 12
uart1:
txd_pin: gpio.1
rxd_pin: gpio.2
rts_pin: NO_PIN
cts_pin: NO_PIN
baud: 115200
mode: 8N1
spi:
miso_pin: gpio.13
mosi_pin: gpio.11
sck_pin: gpio.12
sdcard:
cs_pin: gpio.10
card_detect_pin: NO_PIN
frequency_hz: 8000000
kinematics:
Cartesian:
axes:
shared_stepper_disable_pin: NO_PIN
shared_stepper_reset_pin: NO_PIN
x:
steps_per_mm: 80.000000
max_rate_mm_per_min: 2000.000000
acceleration_mm_per_sec2: 25.000000
max_travel_mm: 2438.399902
soft_limits: false
homing:
cycle: -1
allow_single_axis: true
positive_direction: true
mpos_mm: 0.000000
feed_mm_per_min: 50.000000
seek_mm_per_min: 200.000000
settle_ms: 250
seek_scaler: 1.100000
feed_scaler: 1.100000
motor0:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000000
null_motor:
y:
steps_per_mm: 80.000000
max_rate_mm_per_min: 2000.000000
acceleration_mm_per_sec2: 25.000000
max_travel_mm: 1219.199951
soft_limits: false
homing:
cycle: -1
allow_single_axis: true
positive_direction: true
mpos_mm: 0.000000
feed_mm_per_min: 50.000000
seek_mm_per_min: 200.000000
settle_ms: 250
seek_scaler: 1.100000
feed_scaler: 1.100000
motor0:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000000
null_motor:
z:
steps_per_mm: 100.000000
max_rate_mm_per_min: 400.000000
acceleration_mm_per_sec2: 10.000000
max_travel_mm: 100.000000
soft_limits: false
homing:
cycle: -1
allow_single_axis: true
positive_direction: true
mpos_mm: 0.000000
feed_mm_per_min: 50.000000
seek_mm_per_min: 200.000000
settle_ms: 250
seek_scaler: 1.100000
feed_scaler: 1.100000
motor0:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000000
tmc_2209:
uart_num: 1
step_pin: gpio.15
direction_pin: gpio.16
disable_pin: NO_PIN
r_sense_ohms: 0.110000
run_amps: 1.000000
hold_amps: 0.500000
microsteps: 1
toff_disable: 0
toff_stealthchop: 5
use_enable: true
addr: 0
run_mode: StealthChop
homing_mode: StealthChop
stallguard: 0
stallguard_debug: false
toff_coolstep: 3
motor1:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000000
tmc_2209:
uart_num: 1
step_pin: gpio.46
direction_pin: gpio.38
disable_pin: NO_PIN
r_sense_ohms: 0.110000
run_amps: 1.000000
hold_amps: 0.500000
microsteps: 1
toff_disable: 0
toff_stealthchop: 5
use_enable: true
addr: 1
run_mode: StealthChop
homing_mode: StealthChop
stallguard: 0
stallguard_debug: false
toff_coolstep: 3
control:
safety_door_pin: NO_PIN
reset_pin: NO_PIN
feed_hold_pin: NO_PIN
cycle_start_pin: NO_PIN
macro0_pin: NO_PIN
macro1_pin: NO_PIN
macro2_pin: NO_PIN
macro3_pin: NO_PIN
coolant:
flood_pin: NO_PIN
mist_pin: NO_PIN
delay_ms: 0
probe:
pin: NO_PIN
check_mode_start: true
macros:
startup_line0:
startup_line1:
macro0:
macro1:
macro2:
macro3:
start:
must_home: true
deactivate_parking: false
check_limits: false
parking:
enable: false
axis: Z
target_mpos_mm: -5.000000
rate_mm_per_min: 800.000000
pullout_distance_mm: 5.000000
pullout_rate_mm_per_min: 250.000000
user_outputs:
analog0_pin: NO_PIN
analog1_pin: NO_PIN
analog2_pin: NO_PIN
analog3_pin: NO_PIN
analog0_hz: 5000
analog1_hz: 5000
analog2_hz: 5000
analog3_hz: 5000
digital0_pin: NO_PIN
digital1_pin: NO_PIN
digital2_pin: NO_PIN
digital3_pin: NO_PIN
digital4_pin: NO_PIN
digital5_pin: NO_PIN
digital6_pin: NO_PIN
digital7_pin: NO_PIN
NoSpindle:
arc_tolerance_mm: 0.002000
junction_deviation_mm: 0.010000
verbose_errors: false
report_inches: false
enable_parking_override_control: false
use_line_numbers: false
planner_blocks: 16
Nothing there jumps out at me as being weird, but it does give me an idea for something to try.
Lets try tweaking the size of the grid.
Can we try something super basic and little like a 3x3 grid that’s 300x300mm?
OK, sounds like a way forward. I’ll try that and let you know results. Thanks for the assist!
Just tried this twice. The calibration started low on the board, a third off the edge, ran for maybe 30 seconds, stoppped with a red flashing light, no real error messages I could see (the first Log)
Serial Messages
Index.html Version: 0.87
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v0.79 (Maslow-Main-7b9f3a44-dirty)]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[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: STA SSID is not set]
[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:ERR: Not handling localfs subdirectories]
[MSG:INFO: Telnet started on port 23]
Log ended here.
Tried one more time and got a surprising number, then a STOP - at the end
[MSG:INFO: Center point deviation: TL: -0.032 TR: -0.028 BL: 130.508 BR: 13.582]
[MSG:ERR: Center point deviation over 100.000mmm, your coordinate system is not accurate, adjust your frame dimensions and restart.]
Here is the full log:
Serial Messages
Index.html Version: 0.87
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v0.79 (Maslow-Main-7b9f3a44-dirty)]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[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: STA SSID is not set]
[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:ERR: Not handling localfs subdirectories]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Caution: Unlocked]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Bottom Left pulled tight with offset -1652.595]
[MSG:INFO: Top Left pulled tight with offset -1700.746]
[MSG:INFO: Bottom Right pulled tight with offset -1701.723]
[MSG:INFO: Top Right pulled tight with offset -1814.334]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: -0.032 TR: -0.028 BL: 130.508 BR: 13.582]
[MSG:ERR: Center point deviation over 100.000mmm, your coordinate system is not accurate, adjust your frame dimensions and restart.]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
Could the BL servo or circuit board have a problem?
Also I just noticed in another post DLang referred to “did you do the rehang dance (retract/extend/tension)” . I just reviewed the Calibrate Youtube video and actually it shows (retract/extend/calibrate). Is that the same thing?
Second thing, in the video it appears you have the spoil board mounted lower in the rectangle formed by the frame. Proportionally mine looks closer to the top, almost upside-down from yours. Does this orientation matter?
Johnnie Eskue wrote:
Also I just noticed in another post DLang referred to “did you do the rehang
dance (retract/extend/tension)” . I just reviewed the Calibrate Youtube
video and actually it shows (retract/extend/calibrate). Is that the same
thing?
the rehang dance is retract/extend, calibration should only need to be done if
the frame changes (or to see if improved firmware generates better results)
Second thing, in the video it appears you have the spoil board mounted lower
in the rectangle formed by the frame. Proportionally mine looks closer to the
top, almost upside-down from yours. Does this orientation matter?
The maslow assumes that the work area is centered on the frame.
David Lang
Noted you are running v0.79 for FluidNC and V0.87 for Index.html.gz
Thank you for the clarification. I’ll fix the rack so that is no concern.
Ooops. Good catch, thank you! I’ll fix that. Looks like I have a couple of things to do. Making a list, checking it twice… will be a couple of days to get to it, need to take my wife camping for a bit. Thank you for all the help! “I’ll be back.”
Beginning to suspect a loose magnet myself. Can’t imagine anything else causing such random wild numbers. I could be wrong (again) but the router did get a hard bump at least once since I assembled it. If this is a real possible fix, I’d rather do that than waste all of your time.
I went through something similar last summer…the Maslow 4 would often come very close to passing calibration (and on a couple of occasions did), then throw those kinds of errors.
When I finally, grudgingly took my arms apart, I found more than one magnet loose, and found grub screws that had backed out from the idler or driven gears in a couple of unfortunate places.
I wish I had thought then to also check the driven gear/idler gear for binding…once I got the magnets sorted out and the grub screws in their proper places, I was able to cut, but the longer the cut the likelier that it would lose position. Once I shifted the drive motors away from the idler gear (by a fraction), things got pretty good.