Hi guys
Recently updated to v3.9.9 version of FluidNC so I can access files with Jason’s FluidTouch.
Now seeing these warnings in orange with the recommended firmware. Have I stuffed up here or is it an easy fix to just specify a “homing current” for the motors?
Also a bit offended that my ESP32 has been called -dirty on line 2??
Any advice appreciated.
I would make a backup of your config.yaml file first, but yes, you could just add a homing_amps to the config for each motor:
run_amps: 0.800
homing_amps: 0.800
Or, you could update to the latest version of the config.yaml. If you post your current config.yaml, we could compare to see if any other changes are necessary.
I’ll also note you are on WebUI v2. You could update to WebUI v3 but you do not have to. In WebUI v3, these warning don’t result in a popup display like WebUI v2.
Did you update the firmware through the web installer? The intent was that custom builds outside of the Git repo would display this flag so the FluidNC devs would know that this was modified firmware. However, I think somewhere along the way, that stopped working and now it always shows dirty.
I thought I was using the latest version of the config.yaml file but I will compare with the linked file here. The homing_amps messages were just warnings and I managed to cut out some parts yesterday but I will add a homing_amps line and try that.
Loving your FluidTouch now though. Other than using the WebUI v2 to upload my cut file I control the Low Rider using just FluidTouch and in my opinion it is much more logical than either WebUI v2 or v3.
The “dirty” question was just curiosity but nice to now know how it comes about.
Cheers