Can you copy and paste the error message? That should tell us what the issue is
Maslow_Error_10182024.txt (6.8 KB)
Maslow_Test_Cut_GCODE.txt (3.8 KB)
@bar I went ahead and copied the error message into a .txt file (“Maslow_Error_10182024”.txt") so you can see the full extent of the error. I also uploaded the full GCODE File so you can see that as well.
1 Like
[MSG:WARN: Position error on Bottom Right axis exceeded 15mm while running. Error is 15.041mm
This is the culprit. It’s a pretty common error which happens when there is an interruption in the connection from the controller board to the encoder boards. A quick fix is to blow out the ethernet connectors with compressed air or computer duster and use some hot glue to keep them sealed so dust can’t get in there. A longer term fix is the new JST-XH boards that we just made to solve exactly this issue. The ethernet connectors just aren’t great at handling the dust and vibrations.
Hello everyone, it’s been a little while since I’ve posted on this issue but I wanted to update you all on my progress. Since getting my last response from Bar, I went ahead and ordered the new JST-XH boards along with it’s accompanying connectors and encoder boards. Upon installing all these new components, I am still falling into the same issue as before (See attached .txt file for error), same GCODE is being used. I have also provided a video of where I am seeing the issue present itself.
Maslow_Error_120824.txt (1.2 KB)
@bar @anna I’m about at my wits end here and I thought we had narrowed down the issue to just hardware, however, this doesn’t seem to be the case as clearly i’m getting the same problem as before. I’m inclined to think that perhaps the next course of action is to send this constructed unit to you and have you put it on one of your frames (vertical and/or horizontal configuration) and see if you can get it running. The assumption here is that, if you can get it to successfully run a profile and do what it’s supposed to do, then clearly I have an issue with my frame, but I feel like we need to do root cause analysis on this and identify if the issue is with the unit or somewhere else entirely. Question: Is there a way to open up the tolerancing on the unit to accept a larger error value, then perhaps it would run? Just a thought.
Me too 
We haven’t ever seen that error since switching to the JST-XH connectors.
Does the issue always happen in the bottom left corner of the sheet? Have you ever seen it happen in the center of the sheet?
This is certainly possible, but I think we risk breaking something.
Do you have enough space to try laying it flat (even temporarily) and running calibration in horizontal mode? I think that would be a way to test if we’re worried about frame flex both because 1) If the frame flexes the corners will lift up from the floor which is easy to see, and 2) Laying flat it will be quite a bit more rigid
I’m unsure if the issue happens if the home is in the center of the board compared to in the corner. I’m unable to remove my waste board/frame from the vertical orientation and lay it on the ground unfortunately, hence my looking into shipping my unit to you and seeing if you can run it through a calibration and maybe a test cut. This would at least eliminate the potential that the unit is the issue and would focus the attention on the frame. Allow me to remind everyone that this frame is a aluminum extrusion frame so it’s possible that it may not be rigid enough, at least at first glance and from what is perceptible. I may end up making a new frame out of wood since it’s cheap enough just to see if that fixes the issue.
1 Like
I’m working on a firmware change which can automatically detect how much the frame flexes, hopefully we’ll be able to release that this week which should make it so that you can get a value for how much the frame is flexing.
2 Likes
Awesome, thank you so much! Has this been released yet?
1 Like
It has now!
Good Morning everyone, i’m back! Been a little while since i’ve posted, but that’s because I moved and had to store my Maslow until I was in my new house. Now that I am all moved in, I am ready to jump back on this horse to start using this machine and get some projects done!
First things first, based on all the issues that I had faced initially, I built a new frame that is virtually identical to the one outlined by the folks at Maslow using wood. I have also updated the Maslow to V1.15 Firmware, so we are running the latest version of that.
With that, I attempted to perform a calibration this morning and I am seeing some issues, the first being that the GUI no longer shows “Calibrate” as an option, but instead, “Find Anchor Points”. I assumed these two were the same thing and clicked the “Find Anchor Points” button, to find the process had started, and immediately I could tell there were issues.
For starters, my frame is in a horizontal/flat configuration, and the belts initially started by spooling out slightly, then slowly started to retract. The issue, however, is that some of belts during that unspooling were unwinding away from the center spools rather than out from the motors/encoders. Also, when it did retract eventually, during the calibration process, the belts did not spool back up to a more “taught” configuration, leaving slack while it was taking it’s measurements.
When the machine had ran through it’s initial grid is started performing it’s calculations, but this was a moot point as it would continuously keep trying to iterate, never really settling on a setpoint. Eventually I had to shut the machine down and restart it. I thought I would go ahead and retry the calibration, but upon performing a retract, one of my belt motors decided not to move and retract the belt, so 3/4 belts are retracted and the other is loosely sitting there and unwound.
Here is the serial log from when I turned the machine back on after turning it off from the initial calibration:
Serial Messages
Index.html Version: v1.15
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v1.15]
[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:Batcave]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.68.72]
[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]
Grbl 1.15 [FluidNC v1.15 (wifi) ‘$’ for help]
Grbl 1.15 [FluidNC v1.15 (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: Center coordinates updated in MaslowKinematics: X=2197.631 Y=1647.726]
[MSG:INFO: Current z-axis position loaded as: -30.000]
[MSG:INFO: loadBeltPositions() called]
[MSG:INFO: Validity check: ret=0 validityMarker=0]
[MSG:INFO: Saved belt positions in NVS are marked as stale/invalid (value=0) - machine will remain in UNKNOWN state until belts are calibrated/extended]
[MSG:INFO: Starting Maslow Version v1.15]
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: Caution: Unlocked]
Retract All
[MSG:INFO: Retracting all belts]
[MSG:INFO: Requesting state change from Unknown to Retracting Belts]
[MSG:INFO: Succeeded]
[MSG:INFO: Top Left pulled tight with offset -0.172]
[MSG:INFO: Bottom Left pulled tight with offset -1336.997]
[MSG:INFO: Bottom Right pulled tight with offset -1531.234]
[MSG:INFO: Top Right pulled tight with offset -1793.656]
[MSG:INFO: Requesting state change from Retracting Belts to Belts Retracted]
[MSG:INFO: Succeeded]
Retract All
[MSG:INFO: Retracting all belts]
[MSG:INFO: Requesting state change from Belts Retracted to Retracting Belts]
[MSG:INFO: Succeeded]
[MSG:INFO: Bottom Left pulled tight with offset -0.075]
[MSG:INFO: Top Right pulled tight with offset 0.075]
[MSG:INFO: Top Left pulled tight with offset 27.828]
[MSG:INFO: Bottom Right pulled tight with offset 0.032]
[MSG:INFO: Requesting state change from Retracting Belts to Belts Retracted]
[MSG:INFO: Succeeded]
Thank you for the assistance,
Mark Thomas
It seems to me that your problem is that the arms are too tight, one more than the others. My solution was to disassemble them and sand them down so they could rotate freely by hand, allowing me to work with a force of 800 so the motors wouldn’t interfere with each other.
2 Likes
@bar can you provide additional feedback?
1 Like
I think that @Betalombo is exactly right.
If the belts don’t pull fully tight during the calibration process it won’t get accurate measurements. Picture using a tape measure, if it’s not tight then it isn’t an accurate measurement.
You can increase the force used by the machine to pull tight during calibration in the config menu.