I had a working yaml file and decided to run calibration to see what difference it made
This is on the super simple frame with gussets top and bottom (a very rigid frame)
This frame is ~30” square, a usable working area of 350mmx350mm
I did a 9x9 calibration over the entire area, fitness just over 2
I then tried to jog and it refused saying it didn’t know the belt lengths, that they needed to be retracted (see attached log file)
Then I noticed that all the belts were slack, with the belts way out on the spool, and the top spool was slowly moving (the belt wasn’t moving, it was tangled quite badly.
so something went significantly wrong here, and I have no idea why @bar
both of these belts unwound to the point that the belt doubled back on itself,
one destroyed the belt, the other was stopped by me unplugging the machine in
time.
Looking at the log it looks like this might be related to the issue with running back to back calibrations that someone else reported. I’ve been meaning to investigate it, but I haven’t had a chance.
[MSG:INFO: Requesting state change from Calibrating to Ready To Cut]
[MSG:INFO: Succeeded]
[MSG:INFO: Requesting state change from Ready To Cut to Calibrating]
[MSG:INFO: Calibration starting in HORIZONTAL orientation mode]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Center coordinates updated in MaslowKinematics: X=374.832 Y=376.786]
[MSG:INFO: Machine Position found as X: 0.063 Y: -5.158]
[MSG:INFO: Setting motor positions from hardware readings:]
[MSG:INFO: TL: 389.688 TR: 380.734 BL: 375.666 BR: 372.166]
[MSG:INFO: Succeeded]
Maslow is not ready to move.
Could not perform Jog. Belt lengths are unknown.
Just to make sure that I’m understanding what I’m seeing in the log this was Full Calibration Process → Fished and ready to cut → Pressing calibrate again. Does that match up with what happened?
Looking at the log it looks like this might be related to the issue with running back to back calibrations that someone else reported. I’ve been meaning to investigate it, but I haven’t had a chance.
[MSG:INFO: Requesting state change from Calibrating to Ready To Cut]
[MSG:INFO: Succeeded]
[MSG:INFO: Requesting state change from Ready To Cut to Calibrating]
[MSG:INFO: Calibration starting in HORIZONTAL orientation mode]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Center coordinates updated in MaslowKinematics: X=374.832 Y=376.786]
[MSG:INFO: Machine Position found as X: 0.063 Y: -5.158]
[MSG:INFO: Setting motor positions from hardware readings:]
[MSG:INFO: TL: 389.688 TR: 380.734 BL: 375.666 BR: 372.166]
[MSG:INFO: Succeeded]
Maslow is not ready to move.
Could not perform Jog. Belt lengths are unknown.
Just to make sure that I’m understanding what I’m seeing in the log this was Full Calibration Process → Fished and ready to cut → Pressing calibrate again. Does that match up with what happened?
no, if calibrate was hit a second time, it was well before the calibration
finished.
Let me also reply on this one. I seem to have similar issues. Did the calibaration, everthing went well. I managed to cut my first piece!
today, got back, simply try to move maslow to the home position and I get:
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:G21haha]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 10.215.247.139]
[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]
Maslow is not ready to move.
[MSG:INFO: Caution: Unlocked]
Maslow is not ready to move.
Maslow is not ready to move.
Stop Maslow and Gcode
Maslow is not ready to move.
Could not perform Jog. Belt lengths are unknown.
Maslow is not ready to move.
Could not perform Jog. Belt lengths are unknown.
[MSG:INFO: Caution: Unlocked]
Maslow is not ready to move.
Maslow is not ready to move.
Stop
[MSG:INFO: Caution: Unlocked]
Maslow is not ready to move.
Maslow is not ready to move.
try to hit alarm/move home/… few times, but no response except ‘maslow is not ready to move’.
I updated to the latest firmware/index.html few days back so I don’t expect that to be the issue… Any ideas?
Also, when a cut is finished, and I want to switch the bit I hit the ‘release tension’ button, but I’m never able to apply tension again; seems I always have to perform full retract/Extend/calibration/…
wat are the exact steps I have to perform to replace the bit (I was expecting a simple release tension, replace the bit, apply tension) but that doesn’t seem to work… Also, when I give power again, what are the steps I have to perform to be able to cnc again?
That should be all you need to do, the power just needs to stay on the whole time.
Whenever the machine loses power it loses track of the length of the belts. To start cutting again you need to Retract All (so the machine knows the zero length of the belts), Extend All, and then Apply Tension
Retract all (2x cause the left under motor didn’t work 1st time)
If you have one belt not reliably retracting, you need to increase the
retraction current limit until it reliably retracts all the way with a single
effort.
Note that there are two current limits.
retraction current, used when fully retracting the belt
calibration current, used to pull the belts tight when hooked to the frame
it’s possible that retraction current needs to be higher than calibration
current as the full spools can rub against things at the very end in a way that
they don’t when hooked to even a small frame
If one arm needs significantly higher force to pull tight, it’s not a bad idea
to take that arm apart and check that everything moves cleanly, it may require
sanding the inside of the spool just slightly so that it moves more smoothly.
also check that the gear on the motor isn’t rubbing the plastic.
That should work, but you need to raise the bit prior to release tension, as I don’t think you can adjust Z values when belts aren’t tensioned, then retension and readjust for Z home after bit replaced. Also you may need to set up multiple jobs, one for each time you change the bit. The Maslow is very good at getting back to the home position and repeating cuts accurately.
