I am very late to the game with Gsender and learned a lot on this forum, However, I cannot find how to let Gsender know the location of my Bitsetter. Can anyone instruct me exactly how to do that? I would be very greatful. Thanks, Tom
You have to first enable the “Fixed Tool Sensor” as part of the Tool Change Strategy, and then the configuration for location of the sensor (ish, discounting Z) magically appears 
.
Thanks so much, I found this page just 5 mins ago and did exactly that. I then move my machine to center of table and I asked the macro that everyone has installed, to go to initial tool measure but unfortunately it does not go that location that I setup in tool changing. Not sure what I am doing wrong.
Pretty sure this config setting only works for the built-in gSender tool change strategy - a macro would have it’s own internal configuration. May be a question for Sienci as to whether or not macros can access variables in gSender that aren’t saved in corresponding controller registers ($number things, since we’re still programming in the 80s here).
See my other thread, I’m also trying to understand how all of this stuff inter-mixes currently and it’s confusing as heck. I don’t believe there is a way to just interactively trigger a tool change (per your “go to the middle of the table and run the macro”) which is a bit confounding - I think it can only be tested/validated in the context of running a program, but I have more work to do to understand this. It’s definitely not clear or user friendly to get this stuff bootstrapped.
@tq55 as @drilling-vagueness said, if you’re planning to use your own macros then you’d have to set the location of your BitSetter through those macros. The setting @drilling-vagueness showed is only if you use our built-in g-code tool change wizard which, for the record, should also work with the BitSetter - but I can understand if people want to customize their setup more than the built-in wizard offers
2 Likes