Upgraded to version 1.2 of the firmware and having some Issues.
When cutting the bottom belts are slack where previously they have been under some tension.
My frame is just a bit smaller than the stock frame in vertical configuration. Calibration setting was 800x800 and 7x7 - all went well with a high fitness.
When preparing for cutting:
Retract all - okay
Extend all - okay
Hang on frame and apply tension - all belts tighten and ready to cut okay
Then as soon as I home or start any moves the bottom belts slacken, as the top belt pull into position. The bottom belts are never tight and are slack during all moves. Eventually the Maslow stops due to positioning errors. It seems possible the slack bottom belts eventually cause this to happen. Previously the bottom belts have remained taught and definitely no slack.
As an experiment I attached some additional weight to the bottom belts to see if manually adding some tension would help. Ran the gcode without any fault and no errors.
Do you mean V1.2 or V1.12 (V1.14) is the latest. V1.13 has problems
If you go to Setup, Config what size is your configuration grid. You probably need to run Find Anchor points with a larger Grid. This may give you a lower fitness score, but the Maslow will have a better idea of where it is in relation to the anchors. It may also take longer to finish.
Thanks for the reply David - when it first started I hadn’t changed the yaml file. It just started all of a sudden after fixing a loose encoder cable.
I then reloaded the backup yaml file in case something had become corrupted but the same problem was still present. Ran a new calibration, but no change.
I used 800x800 with a 7x7 grid for the calibration and someone suggested increasing this to something bigger, but in the same aspect ratio as my frame - will give this a try and see what happens.
So - updated from pre v1 using the USB method outlined by Bar. I had real problem after installing v1.13 so flashed v1.12 instead.
Was able to calibrate with a high fitness score and ran a test gcode file without the router bit or router running to check moves. Bottom belts were under some tension and all ran okay.
Ran same file next day with router and dust extraction running and had issues with top left encoder bad connection - it seems that vibration was an issue with the cable connection. Had a number of crashes caused by the encoder issue until I seem to have fixed it with some packing and hot glue. Ran the file again and this was when the issue with slack lower belts started.
Ran a new calibration and the fitness was now better, but as soon as I start any moves the bottom belts unwind slightly and go slack.
Reloaded the firmware and backup yaml again to rule out any firmware issue. Calibrated again,but same problem.
I have a vertical setup running 1.12 firmware but have the 4.1 Maslow so I can’t relate to the old connectors. I’m sure you’ve done the calibration routine many times, retract, extend and then calibration mode. Are the bottom belts on the first few waypoints, 4 or 5 I think, slack when calibrating then every waypoint after that should be tensioned up. I use a grid of 2000x1000 with 800 retract and calibration force. What are yours? Sorry but I gotta throw it out there you did select vertical for orientation right? Have you altered any of the config settings that may have affected the bottom belts? Enabled debug? Could it be the file?
Ran same file next day with router and dust extraction running and had issues
with top left encoder bad connection - it seems that vibration was an issue
with the cable connection. Had a number of crashes caused by the encoder issue
until I seem to have fixed it with some packing and hot glue. Ran the file
again and this was when the issue with slack lower belts started.
if this is with the 4.0 maslow (the ethernet cables), you should use hot glue to
fasten the cables in place on both ends. This is the key reason the 4.1 upgrade
exists.
Reloaded the firmware and backup yaml again to rule out any firmware issue.
Calibrated again,but same problem.
if the backup yaml is the version that let you move around cleanly with the
router off, that should be the anchor coordinates that you should use. Can you
compare those with the results of your new calibration and see how they differ?
Upgraded to firmware v1.14, along with v1.14 of the index.html file and new yaml file. Ran a new calibration using a larger size 1200x600 which is more in proportion to my frame.
Got a fitness of over 1.8.
First cut and no problems with slack lower belts - ran for 40 minutes and completed the job without any issues at all. Very small error in sizing or 0.16% so may try the scaling settings and see if I can get it perfect.
For information:
12mm plywood
4mm single flute upcut endmill
1600mm/min feed rate
200/min plunge
2mm depth of cut
~18000rpm
