@phaedrux @garyd9 in case you'd like a walkthrough of how the current TAMV runs voiced-over by yours truly, here you go: https://www.youtube.com/watch?v=1nGc_hFzK0s&t=5s
I've taken Danal's legacy (I was actually one of the early testers for TAMV over on the Jubilee discord where he started the project), and run full steam ahead with it to make it even more accessible to folks with toolchangers/IDEX machines running RRF. We've come a long way improving on his work, and there's more to come!
That's a really interesting observation and I'm going to run a few tests this week to see if I can find that sweet spot. Multiple speeds and perhaps even changing the chop register on the TMC might yield some improvement. Thank you!
Resurrecting this topic, as I just stumbled upon it..
TAMV has been updated recently (I'm maintaining the Jubilee branch), and has been significantly enhanced. It does automatic detection, semi-assisted detection (where you jog to a crosshair and click a button to calculate, capture, and apply offsets), selectable tool calibration (choose what tools get calibrated), and is now fully multi-threaded for faster execution. Klipper support is also in beta testing (its now an extensible program for any controller). Installing takes about 5 minutes on a pi, since it now uses pre-compiled openCV binaries.
Only thing you'll have a challenge with is IDEX support, as its currently limited to identifying X,Y and Z axes for alignment, where usually idex will require other axes. I haven't extended it to any axis you choose yet as its quite a bit of work, but it works great on Duet 2 and Duet 3 boards, and we're always around on the Jubilee Discord for any questions and help!
We're lacking a little of the fine details on how to run the software, as I haven't caught up with the docs writing yet.
Latest source (use the master branch please):
https://github.com/HaythamB/TAMV
General installation instructions (also on the GH repo):
https://jubilee3d.com/index.php?title=TAMV
Let me know if you want any info! 
semi-assisted mode looks like this.
Forgot to reply and close this out: running beta 2 now, seems to be alright, but the root cause was my hardware and not the controller or the firmware. A slight oversight on my end was definitely the culprit!
Cheers!
@Veti excuse me while I drive to Ben Nevis and take a leap off the top.
Fml, serious case of Dad brain this weekend. Sorry to waste everyone's time for something so damn trivial. I have never been more embarrassed.
@t3p3tony I've tried recreating it by removing the endstop connection, stalling the stepper during homing, etc. etc. but I can't seem to recreate the same error message I've had, and the printer still runs the Z home macro flawlessly. I'm honestly quite perplexed and chalking this one up to RRF beta gremlins 
Thanks for the help in all cases!