After changing the encoders, I was able to do some conclusive tests, but today Error 66 appear before or during the cuts. I don’t know where to find a table of errors to understand, so I’m sharing the logs with you.
Maslow-serial(2).log (3.4 KB)
Maslow-serial(1).log (6.5 KB)
Before that, I used the interface on my iPhone and on my all-in-one and on my desktop PC. On the iPhone, the coordinates were not updating but the movements were fine.
http://wiki.fluidnc.com/en/support/alarm_and_error_codes
Error 66 is a failure to open a file
someimes power cycling will work with this. otherwise, try updaing your
maslow.yaml file (make sure you save the Maslow* variables from your old one to
avoid needing to recalibrate)
David Lang
1 Like
So I updated the yaml file, entered the dimensions of the Machine. Now it doesn’t move in XY anymore. If I ask it to move, I see the coordinates change but it doesn’t move. I updated firmware to latest.
And calibration process ends with
[MSG:INFO: Center point deviation: TL: 0.161 TR: 0.092 BL: -2.687 BR: -93.730]
[MSG:ERR: Unable to move safely, stopping calibration]
And after more tests
[MSG:INFO: Center point deviation: TL: 0.008 TR: 0.675 BL: -18.410 BR: -89.216]
BR has always around 100 less offset
[MSG:INFO: Bottom Right pulled tight with offset -1970.544]
[MSG:INFO: Top Left pulled tight with offset -2074.512]
[MSG:INFO: Top Right pulled tight with offset -2083.455]
[MSG:INFO: Bottom Left pulled tight with offset -2039.083]
1 Like
When it won’t move like that it’s because the machine doesn’t know its belt lengths. Running Retract All and then extend all will fix that.
Any time that the machine is turned off and back on that needs to happen
1 Like