Homing Amps :-)

Software / Firmware Jackpot Board / FluidNC
1

At some point (perhaps late last year) a change for the Jackpot board’s FluidNC config.yaml file is that now you can (and should) have homing amps defined. I think it’s in the docs already, and it’s been mentioned in several places on the forum.

Just wanted to mention that until recently I had not yet noticed anything about this, and I stumbled onto it a few days ago, and so I got homing amps added/specified in my config.yaml, and I made sure the Z was a little stronger, and I saw an immediate benefit in that, before, sometimes when I would home my LR4, the Z would make a grinding sound and not move upwards unless I gave it a nudge, and now with the higher homing amps on Z… that issue does not happen any more.

For X and Y I set it to:
homing_amps: 0.500

While for Z I made it match my run_amps at 0.68:
homing_amps: 0.680

…So if you’re like me and you had not heard about this, and you have an occasional Z homing issue with grinding and lack of motion, edit your config.yaml!

4 Likes
2

That reminds me that I was going to diff my config.yaml against the current ones since mine is based off an older revision. There’s been a few changes. I think in the current config, it homes X and Y at the same time too.

Git blame is a good way to see what changed when.

2 Likes
3

I had heard about “blame” and “blaming” but did not realize what it was!

1 Like
4

It’s when someone tells you it’s your fault. :yum::sweat_smile:

3 Likes
5

Ha, well for my job, I usually use it to see what changed when but it does tell you who made the last change to each line of code. For me, it doesn’t really get used to blame someone. If a change broke something that made it through dev, review, and QA testing, we don’t normally mock the dev (sometimes in good fun or making fun of yourself).

2 Likes