You’re right! After setting that value, I hit refresh, and the new value was there. I then downloaded maslow.yaml to my laptop, and opened it in a text editor. Lo and behold, the value there was still 1300.
I updated the maslow.yaml file and uploaded it into fluidnc. Is it sufficient to restart fluidnc, or do I need to power cycle the maslow controller?
Yes. I tried retracting again after the upload and restart. Nothing. I power cycled and tried again. This time a second belt retracted. Further presses of the retract all button only results in momentary running of the cooling fan.
Shall I try a higher value of retract current? How high is safe?
In the FluidNC settings tab, there are ‘flash settings’ and ‘config settings’ the popup hint says that the flash settings are immediately changed, and the config settings are saved only on command. Yet both groups have a ‘set’ button next to each value. Is there supposed to be a separate ‘save’ button to rewrite the current settings into the maslow.yaml file?
Before going higher let’s try clicking Extend All after Retract All and give the belts a little tug. Do they extend out?
The max value that Id feel good about going up to is maybe 2500.
FluidNC is an awesome project, but it’s got some quirks and weirdness that I can’t say I’ve fully figured out. One of the limitations is that I believe right now it can’t actually edit the .yaml file directly. As far as I know the only to actually have a change save to the .yaml file is to edit it directly. That’s high on my todo list for software features because it’s super annoying.
OK. I hit extend all, and pulled each belt out about a foot before I hit stop.
then I reset the alarm, re-entered setup, and hit retract all. this time three belts retracted.
I tugged a bit on the one remaining belt, then hit retract again. this time the final belt retracted fully.
This is all with the retract current threshold set at 1800 still.
That’s all I can do now, I have to go build a frame before I continue…