This is a bit faster than expected, but, we are happy to announce that we are releasing the new CutControl 25.1.2 as a Beta a couple days early. This has been a long time coming and I hope that everyone enjoys the new features and bug fixes.
This new version of CutControl will include the following:
Multi-line Manual Data Input
Adjustable safe Auto-Toolset
Visual changes to accommodate new features
Touch Probe sequence no longer resets Work Coordinates
Machine firmware properly updates
This will be a beta release for the moment and will only be available here, if you have any issues or encounter any bugs it would be helpful if you posted here and included a short description along with ways you have been able to replicate the bug.
The tool setter is broken from what I can tell. I get a constant “not triggered within the program travel” The thing is the z height is different every time the error triggers. so… I had to set the safe zero to -3 to get it to work. there is nothing safe about -3" The tool setter is not useable at all for me considering it has to be set at -3. I’ve tried different combinations for 30 minutes now.
Also, none of the other “new” features are ones that I care about so I’ll have to go back to the old version. Of all the wish list things people posted about over the last year, we got none of them. We ended up getting a “write your own G-code program” feature that I don’t think I saw even a single person ask for… it’s 2025, nobody is writing custom G-code programs. Conversational programing might be useful.
Also that button you’re forced to hit when your program is done before you can run the program again is still freaking there. Dang! There is nothing I hate more than that dang button. I literally paid my 9 year old one night to hit that dang button for and hour while I ran parts.
It’s possible I just don’t know how to configure the new tool setter. Please advise.
Hey @Richarddbeck83, does the first touch off work for the tool setter but you see the error on the second fine touch? If so then I’ve seen that crop up a few times before now and it’s been a tool setter/grounding issue instead of software.
I checked with Zach this morning and he’s been able to verify that the tool setter cycles run correctly on two different MR-1s. Feel free to shoot us an email or DM me and we’ll get it squared away.
The first touch doesn’t make it to the tool setter in time. what are Zach’s safe z numbers? I could try those.
So it’s not triggering before the touch like it did back when I had voltage leaking but it says it did not trigger in the allowable travel distance. So if I lower it’s starting point (safe z) then it makes it to the tool setter. The calibration with tool works just fine when traveling the same distance.
I have seen this problem many times in Cut Control 24.1.1. I then had more issues with the tool setter, and ultimately found corrosion in the tool setter. mostly a green corrosion on the plug and socket. It is working better after cleaning and using some dialetric greese on the plug. I don’t think the top rubber cap does a good job of keeping humidity out. I just istalled 25.1.1 but have not run it yet.
Thank you for the update.
so I have a work around. Your total Z distance traveled during the auto tool set sequence needs to be less than around 5.80" ish. So if your tool setter is down low you have to raise the z high enough before you trigger the auto tool set button so the distance up plus the distance back down is less than around 5.75" combined.
Also if you’re positioned above the tool setter and maxed out on the z+ you might get a G code exceeds travel error that forces a re-homing of the machine. This is what I’ve found so far after a couple hours of troubleshooting.
I am also finding that bringing up the screen to manually enter a distance or speed, it comes up relatively dark and button presses do not show although the entry does show up in the box for distance or speed.
I will wait to download this version until you guys figure it out. 24.1.1 works perfectly for me. I do wish all the safety screens were limited to real issues and not protecting idiots.
I was all set to put it on my MR1 computer this morning when I read @Richarddbeck83 thread at 5 a.m. Thanks, buddy.
I’ll be doing a litany of tests to replicate this so we can get it fixed for actual release. I’m surprised my testing didn’t quite catch this, but based off the description I should be able to nail it down fairly quickly. I’ll hopefully have some news for y’all later today.
I concur with @Bigdaddy2166. Since I use the MR-1 daily in a professional environment we can’t be down because of a software issue. Thank you @Richarddbeck83 for catching this I’ll be waiting and reading the post as they move forward with the software
I echo @Bigdaddy2166 and @billh68.
I was going to give is a go this weekend, but given the errors found already I’m going to hold off testing it until round 2 maybe. @langmuir-zachary what are the odds we can get a reduction in the amount of pop up windows with this release? Like when jogging to a soft limit, program end, probe cycle complete yada yada. I’m wearing out the center of my touch screen
Can’t make any promises, but I’ll see what I can do about the pop-ups. And completely understand the hesitance in getting the beta, by the time the official release comes out all of these hiccups should be resolved.
I second the thing about the popups. Maybe for liability and CYA, yall could condense the safety wanings into a one-time popup that happens on startup at the homing screen instead?
It’s not that the pop-ups are so bad it’s that they lock you out of any other actions and force you to hit a super tiny button (extra clicks) before you can proceed. If the machine said operation completed successful but then the pop-up went away when I touch any other button on the screen I wouldn’t care.
The pop-ups that you feel are mandatory should just have a really large click area. If hit within 1.5" of the button the intent is clear and the pop-up should go away.
Just ask yourself (could this action be completed with less clicks) for every single machine operation. Every single click you eliminate makes the user experience better. Every click is just wasted time and added frustration.
In stead of asking “do you want to do this action” and forcing a tiny button push a pop up should be “this action is happening” with a big stop button. when the action is over the window self clears.
