Probing only works on Z axis. Probing attempt on X axis the cnc head continues to move in the -X direction until it errors out. Machine set for GRBLHAL. Using AutoZero Touchplate which works flawlessly using Gsender from Scienci Labs
Can you share a screenshot of your probing config, so we can take a look? Alternatively, exporting your device bundle would be great as well (Devices button > Export)
devices export.mmzip (4.9 KB)
I hope to be able to use the Auto Zero Touchplate from Sienci Labs that I use with my Longmill MK2 CNC. The block uses the inside surfaces for probing the X and Y axis. Is there something in setup that I am missing?
Here is the reply I received from Sienci Labs regarding the “Auto Zero Touchplate” which I use on my Longmill MK2. -
The AutoZero touch plate is usually compatible with 2-wire, NO probe connections.
We also have macros that you can load into your specific g-code sender, in order to conduct automated probing processes. You can find these here: Touch Plate - LongMill MK2 CNC
There are several G-code macro samples, however I have only succeeded in getting either the X-axis, or the y-axis macro to work. A macro that will set X, Y, Z in one step would be very nice. In the mean time I continue to do the probing using Gsender and then set the Millmage workspace to 0,0,0 and move forward.
Hi all, I’ve had my LongMill 48x30 for a while now but have been doing very basic projects while I wait for Millmage since I really like LB for my laser. Regarding the probing with the auto-zero touch plate from Sienci, are there any new advancements to utilize it out of Millmage, or would I be just as good to continue using their GSender? It works great there.
Hoping to really get going on designs and if I need to export GCode out of Millmage, that’s fine. Just figured I’d ask.
Thanks.
I’ll give that probe block a go during the next few upcoming projects. Good looking out!
1 Like
Any luck on this? Would really like to use the Sienci autozero touchplate with Millmage.
Same. I really like Millmage for design, but it just may take a while to catch up to the long-term SW packages already out there.
@eilerstg we aren’t rolling out a full advanced feature set on first release simply because unlike most SW packages out there, we are supporting CAM and control on a wider range of controllers than other senders. And given the risk of injury/damage, we want to take it slow and be absolutely certain our logic paths and gcode outputs are consistent so our users can expect a (relatively) safe operation of their upside down blenders on a robot gantry. We will get there, but understand that we’re being cautious about this.
Thanks for the reply and update! Understood and makes total sense.
2 Likes
We’re going as fast as we can! As an Altmill user, I also want this, so you’ve got a vote on the inside 
1 Like