@Able i really like this method. Is it always consistent? Do you only zero once the jaw is loaded so there is no discrepancy between the preloaded jaw and unloaded?
The fixed side jaw never moves so once I use my conductive probe to set my WCS it stays perfect unless I accidently get a chip stuck under my tool length probe or miss steps on an axis.
This required modeling my stock and vise setup in fusion and locking everything down with joints so the models can’t shift.
It was a bit of extra work but it paid off as now that I have saved the WCS as a preset in Carbide motion. When I need to run this job I know as long as the vise setup is bolted down in those positions I can use the preset and run. Before running if I have ran other jobs I jog to zero to confirm first.
I have 4 different setups that share the same WCS and Fusion lets me post process paths from all 4 in one gcode file but it does spit out a warning in regards to having multiple WCS but I know it is shared by every setup and all my tool paths and rapids will clear so I run it.
@WillAdams how do you work around the conductivity issue of having an aluminum fixture plate and setting the BitZero upside down on the aluminum stock to probe a previously machined hole for zero on 2nd OP?
As soon as I touch the plate to the stock the indicator turns red since the fixture plate is connected to the aluminum extrusion which is grounded.
Put a sheet of acrylic or some other non-conducting material down beneath the stock.
@WillAdams ahh I see. I can’t do that. I am holding the stock with ModVices.
This is one of the reasons I moved away from Carbide Motion and the stock controller. It can be expensive but a new controller has been the best upgrade I have done to my machine. You could probably figure out a way to do probing with an inexpensive spindle probe if you used a different gcode sender like Gsender. That just requires a little wiring and learning how to make your own probing routine. No expensive new controller.
Yeah I am now going to try Gsender. I downloaded it earlier today and played around a little bit and I like the ability to customize some things.
I updated to CM latest build and the machine started jumping and stuttering in the corners which obviously ruined the part. I only updated to see if it would solve the issue we have been having with the Z zero being way off after probing or using bit setter.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.