Yes the Initial and New tool macros are from where you show, however Somewhere I found a .json file which had both in one file and I edited that in visual studio to input my bitsetter machine coordinates:
here is a drpbox link to the exact .json file I imported into the g-Sender macro section:
This created the buttons and named the buttons in G-Sender automatically.
If you can start with that file and get me started on converting it to a macro that FluidNC understands that would be great.
The specific Macros above eliminate some of the pauses required if you have to hook up an alegator clip to the endmill etc. The bitsetter is a mechanical solution where the ground and positive wire are inside the bitsetter so no need to connect a ground wire to the spindle.
Also on a side note I have the spindle grounded to earth ground the same as the jackpot so even when I use the touch plate I don’t need to connect a ground to the spindle with a clip or magnet, ground is already connected to the spindle and therefore the endmill.
I didn’t plan to convert the whole thing, but I got drawn in and once I did the first script, the second one was quick.
You want the gcode files without the “_GSender” in the filename. Those were just what I extracted from the JSON file (replaced \n with return, \t with 2 spaces, and \" with ").
There’s some extra stuff in there that probably isn’t necessary but I tried to convert it as directly as possible. In the new tool script, I got rid of some local variables because they weren’t used since it was using global variables set in the initial script.
Obviously, I didn’t fully test these, but I did run them using my normal touchplate to make sure they seemed reasonable and didn’t give any errors.
The only change I’d make is to delete the “pause” in the New_Tool Macro.
Since I don’t plan to change tools above the tool setter and I don’t need to add a clip or ground wire this “pause” is unnecessary.
It’s not that difficult using G-Sender on the PC because a pop-up window appears with a resume button…but on Fluid and the Fluid Dial we get an INVALID STATE and a HOLD on screen and must exit the Macro Screen and go to the Information Screen and Click on the Resume button.
Those are three extra steps that could introduce errors.
Would I only need to delete this from the New_Tool_Bitsetter.gcode?
;Pause for manual tool change & probing
M0
Once confirmed and changed, I’ll upload a video using the FluidNC version of Bitsetter with the FLUID Dial.
Not sure about the invalid state part but otherwise you can resume in the WebUI. But yea, a bit awkward. For WebUI v3, I created an extension that will show the last info message in a popup with a resume button. Then for my wireless pendant thing, it has similar functionality automatically showing the last message with the button pre-highlighted to resume.
Cool. I’m still wondering if we can get this to work as an M6 macro but I think that’s a win for now!
I’m taking notes on features I might want to add when I upgrade my Lowrider. This is on my list. Surely not a necessary feature by any means but I like to play with stuff like this.