Hello,
Just built a 4.1, firmware 1.16.
I am trying to calibrate for the 1st time.
Retract all, Extend all (1750mm), put belts on corner pins, click Find Anchor Locations button. From there the belts go tight, but then all 4 endlessly very slowly extend and it stays in this state. The belts eventually foul and make a bird nest in the spools. Why is it entering this slow extend state and not calibrating?
Haven’t seen this before. Presume you mean Find Anchor Locations, not Calibrate. Calibrate was several iterations ago now. Can you press Test from the Setup Menu and copy paste the result here. Just want to make sure you have the latest firmware and index.html.gz files.
Yes Find Anchor Locations, edited post to clarify. I can get this later today, thanks for the help!
I vaguely do remember having seen this before (although not in a long long time). Ah I even found the thread:
A lot of the things that we suggested there (like changing the grid size) are fully automated at this point so you don’t even need to mess with those settings anymore.
Can you post a copy of the log file?
What happens if you pull out on the belts to let them extend?
Firmware (bin, yaml, html) is v.1.6 from github dotcom /MaslowCNC/Maslow_4/releases.
I let it go, all 4 unreel at 1 tooth per second, when it gets to the end of the belt it starts to wrap up backwards and I stopped it.
Test:
$/kinematics/MaslowKinematics/trY
$/kinematics/MaslowKinematics/trZ
$/kinematics/MaslowKinematics/tlX
$/kinematics/MaslowKinematics/tlY
$/kinematics/MaslowKinematics/tlZ
$/kinematics/MaslowKinematics/brX
$/kinematics/MaslowKinematics/brZ
$/kinematics/MaslowKinematics/blZ
$/kinematics/MaslowKinematics/trX=nanok$/kinematics/MaslowKinematics/trY=nanok$/kinematics/MaslowKinematics/trZ=56.000ok$/kinematics/MaslowKinematics/tlX=0.000ok$/kinematics/MaslowKinematics/tlY=nanok$/kinematics/MaslowKinematics/tlZ=100.000ok$/kinematics/MaslowKinematics/brX=nanok$/kinematics/MaslowKinematics/brZ=78.000ok$/kinematics/MaslowKinematics/blZ=34.000ok$TEST
[MSG:INFO: Firmware Version: v1.16][MSG:INFO: I2C Timeout: ][MSG:INFO: 10][MSG:INFO: All tests passed on Top Left][MSG:INFO: All tests passed on Top Right][MSG:INFO: All tests passed on Bottom Left][MSG:INFO: All tests passed on Bottom Right]$MINFO
[MSG:ERR: AutoUpdate: API request timeout]okMINFO: { "homed": true, "calibrationInProgress": false, "tl": 0.0107361, "tr": 0.0214722, "br": -0.0107361, "bl": -0, "etl": nan, "etr": nan, "ebr": nan, "ebl": nan, "extended": false }ok<Idle|MPos:nan,nan,0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,-75.000,0.000,0.000>
I can’t upload a file, but here is all the text from the Maslow part of the page where it outputs info, while this all happened (retract, extend, find, unreeeeeeel):
Serial Messages
Index.html Version: v1.16
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v1.16]
[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 (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-4000.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.11]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.11]
[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:xxxxxxx]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.1.227]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:xxx]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
Grbl 1.16 [FluidNC v1.16 (wifi) ‘$’ for help]
Grbl 1.16 [FluidNC v1.16 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|‘$X’ to unlock]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:INFO: Motor detected on Bottom Right]
[MSG:INFO: Current z-axis position loaded as: -80.000]
[MSG:INFO: Saved belt positions in NVS are marked as stale/invalid (value=0) - mach
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.11]
[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:xxxxxxx]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.1.227]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:xxx]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
Grbl 1.16 [FluidNC v1.16 (wifi) ‘$’ for help]
Grbl 1.16 [FluidNC v1.16 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|‘$X’ to unlock]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:INFO: Motor detected on Bottom Right]
[MSG:INFO: Current z-axis position loaded as: -80.000]
[MSG:INFO: Saved belt positions in NVS are marked as stale/invalid (value=0) - machok
Extend All
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: Extending all belts]
[MSG:INFO: Requesting state change from Unknown to Extending Belts]
[MSG:INFO: Cannot extend the belts until they have been retracted]
Retract All
[MSG:INFO: Retracting all belts]
[MSG:INFO: Requesting state change from Unknown to Retracting Belts]
[MSG:INFO: Succeeded]
[MSG:INFO: Bottom Right pulled tight with offset -233.746]
[MSG:INFO: Top Left pulled tight with offset -956.005]
[MSG:INFO: Bottom Left pulled tight with offset -967.998]
[MSG:INFO: Top Right pulled tight with offset -409.614]
[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: Succeeded]
Download the V1.16 again, in case it was corrupted, and I suggest you try reloading V1.16 index.html.gz from the FluidNC Drop down menu and the Green button and firmware via Orange button from the new source.
If you still have the same problem, download V1.15 and load it to your Maslow, if that plays up, I’m thinking control board problem.
Belts should not extend unless you are pulling on them, so if they start to move without pulling, there is a problem, so power off before it tangles
You could also try loading via the USB port. This Utube video explains process, just substitute V1.16 for when it says V1.01. If your machine’s sofware was prior to V1.00 this may explain your problem.
Ian Abbott wrote:
Belts should not extend unless you are pulling on them, so if they start to
move without pulling, there is a problem, so power off before it tangles
They should not be, but I’ve experienced it doing exactly that in the past and
never was able to track it down.
David Lang
@dlang What made it stop doing that? Did it just go away on it’s own?
Bar wrote:
@dlang What made it stop doing that? Did it just go away on it’s own?
I never did figure it out for sure. It was very intermittent and
while I saw it a few times (with different releases), I was never able to
reproduce it, even on the same version.
This was around the time I created the watchdog patch. I think the system was
crashing with the motors not set to stopped.
David Lang
I think the reflash was the fix, purged local PC copies of yaml, bin, html. Re-uploaded as Ian mentioned (green, orange +yaml). Retract, extend, find.
After some time, a few times, “ready to cut” and I can drive it around with the arrows and bullseye is center on my frame!
Thanks all for the boost across the finish line, great to know there is a community here to help.
Kyle
Glad it is working for you. The bullseye is where your XY home is Redifine by jogging to where you want home to be and click on define XY Home.