Admittedly new to Carbide Motion but I have been in the software industry for about 30 years.
I have a Pro XL with the Bit Setter as well as the Bit Zero V2.
First a question or two: Why does the jog menu show up sometimes and not at other times? It seems like being able to move the cutter is something you may need to do at any time except when it is actually executing a job. Meanwhile the big red stop button is available even when the machine is not doing anything – shouldn’t it be grayed out when there is nothing to stop? And lastly, CM tends to unceremoniously crash a fair amount.
OK, so on to tonight’s adventure. I have build 566 installed on a Microsoft Surface tablet running Windows 10. I connected it to the cutter. My job is a simple vCarve with a single #301 vee bit. I have the height of my workpiece set to the top (.75"). The cut depth is set to 0.2"
I used the Bit Zero to set my my workpiece’s X,Y and Z.
I checked in CM settings that “PROBE” showed up when I manually pressed on the button of the Bit Setter.
I put my #301 Vee bit in the router.
I loaded the job and started it. The cutter immediately went over to the Bit Setter and lowered the cutter to touch the Bit Setter button twice (I saw the red light come on twice).
The software told me to set the speed to 18,000 rpms. The cutter started and the machine moved over to my work piece and plunged straight down until the bit was completely buried as though it thought the Z was still not to the start point! Arghhh! Luckily this was a test scrap piece. I had to stop the job.
At this point, having the jog commands available would be nice to unbury my bit but alas they weren’t there. The only way to get out of the situation was to hit the initialize button which retracted the bit and went over the right rear corner.
I checked everything I could think of and tried again with the exact same result. I know someone is going to say the definition of stupid is…
Anyway, what did I ever do to Carbide Motion to have it treat me this way? If there is something I did that was obviously wrong I will gladly apologize to the CM team for my remarks but…
Bladen_Owen_1.c2d (152 KB)