This second beta release took a bit longer than I would have liked. But, listed below will be a google drive link to the installer.
This beta V2 includes:
A fix to the Auto Toolset not working above a certain safe threshold.
New Alert bar that keeps a log of most alarms and popups of the current session.
With the addition of the alert bar comes with some popup suppressions which includes, Homing popups, most Limit Switch popups, the Send to Front popup, and the Program Complete popup. This list isn’t final and can be expanded in the future.
This should be a more stable release than the first Beta. But as always, if you find any quirks/bugs report them here or give me a PM.
I really like that status bar! I also love that when the program finishes it says press any button to continue. So the only downside is that even though it says press “any” button it still forces you to hit the tiny “close” button… hahaha It’s like it got my hopes all up than kicked me in the balls. I’m not complaining because we’re headed down the right path.
Also the auto tool setter has a lot more rang than before but still limited and will run out of stroke if you’re down to far when you trigger it. The distance seems to be a lot more than before so I don’t think 90% of people ever trigger the fault now. I was just testing worst case scenario. I think the only reason I have this problem is because I don’t run the tool setter spacer. I run long drill bits and short engraving mills so… With the current range I don’t think it will be a problem. You just might get support request emails about it from people not running the tools setter spacer.
limit switch popups seem to be the same. Still require “close” to be hit. Maybe I’m missing the change. I feel like if the only action that will happen is a warning window closing and you can look back to see what it was, touching the screen anywhere should be able to close the warning window.
Closed programs disappear right away now so that’s fixed.
Ok that first time was the only time I was able to get the auto tool setter to work. I’ve tried a bunch of things and it either gives me a G-code error or it slams the tool into my tool setter and stalls the z axis. When I touch the tool setter it lights up like normal. I don’t have any grounding faults either. I’ve rest the machine and the software. I’ve tried lots of different tool lengths. Calibration with probe and with tool both work as expected. May this is just on my end. Anybody else have issues with the auto tool setter?
Are you able to get the popups to be suppressed or are they still showing up despite them being suppressed? There’ll be a Popups menu in the top left and after accepting the suppression you should stop getting most of the popups related to the item selected.
Key presses from a plugged in keyboard on my end seem to clear the program complete but I’ll still take a look at this on Monday.
On the Auto tool set this is possibly a lack of variation on my part for testing. It still needs some tuning in this case, as it seems to be a firmware limitation in the distance of the seeking operation… unless the error you’re getting isn’t always related to the distance traveled. Which in that case it’s a better question for @langmuir-jake
Otherwise, thank you for the feedback and I hope you have a great weekend as well!
I was busy this weekend and didn’t get a chance to test drive this version. I’m curious about what Richard said with the tool slamming down on the tool setter. Hopefully that’s not a software bug.
If I get back in town at a decent hour today I will see about loading up V2 and checking stuff out. The work on pop-ups is greatly appreciated.
I’ll be taking a look at this today or tomorrow (Mondays are by the far the busiest days), I don’t believe there will be any issues with a large majority of tools. But I plan to at least test with a majority of the tooling that we offer on our store.
o I didn’t see this menu. I’ll check that out tonight when I get home. I’m not sure yet on the auto tool setter. It worked 2 twice than stopped working completely. I’ll have to do more digging to find a pattern. At this point it’s just not working. I’ll get with Jake to see if we can come up with something.
Narrowed down the Auto toolset issue that we are having happen. Will be testing it more thoroughly on Friday. Cleaning up a bit of the Popup issues as well. If everything finishes up well after testing we possibly will be releasing this update by Friday next week.
I had a similar problem to Mr Beck. Auto tool set on 25.1.2 would error out prior to touchoff, but if I set the tool a 1/2 inch above the setter then hit the ATS button, it would climb, rapid down to a little above the setter, then slow down and successfully touch off. I didnt troubleshoot it at all, as I know you guys are working on it. However, if there is any info you need or anything like that, let me know and ill provide it.
one other thing. would it be possible while your messing with the code and all to create a 6 flute chip load drop down? I use 6 flute endmill a lot and really wish I would see on the screen what my chip load is.
Probably a big ask, but can Langmuir add functionality to the UI to do math in the WCS menus? The fact that I cant just add 2” to z for a test run, or subtract 0.003” from Z to bring a chamfer a but lower, gets pretty annoying. A 1/2 function would be good too for when we are finding our origins.
I just finished another few hours of work on the MR1 and have some additional bug sightings…
When you are in any WCS other than G54 and hit STOP to end a program, CutControl automatically reverts back to G54. If you don’t notice this, then you may run a tool offset or zeroing maneuver in the wrong work offset. Very problematic. If I hit stop, it should stay in the WCS that I was last in, not randomly switch to G54.
Additionally, any feed overrides are lost when one hits STOP but not if one allows the program to end naturally. Not good or reasonable for an operator.
Lastly, when you hit STOP the spindle doesn’t turn off. Also very inappropriate for a stop button. Currently the STOP button is no different than a feedpause other than that it also ends the program. Silly.
For WCS resetting, this has been solved in some areas of CutControl but not others. The same reason WCS resets is most likely the same reason Feed Overrides get reset but I was not aware of this, so I will look into it today. These may not come out as an update soon, but it will be added to our list of bugs.
I would reach out to @langmuir-jake as we both tested this in quite a few different scenarios and the spindle stopped when pressing the Stop button. Any more information would be greatly appreciated.
I think there is a problem with the Java installer in 25.1.2. Repeatable on 2 different (Windows) computers - doing initial install from 25.1.2 on a computer which has never had CutControl installed gives a “Failed to launch JVM” error when launching CutControl. Installing 24.1.1 first (thanks for leaving that link up on the web site) runs fine and from there you can install 25.1.2 and it’s happy.
So what do the masses say about this release? Is it worth the upgrade? I’ve been on the original CutControl release becaues I prefer the Devil I Know. But if this update is more stable than that version, I’m eager to switch. I haven’t been able to get accurate results out of my tool setter EVER, so I’m not concerned about those bugs. My tool setter has always been easily over 0.010” off everytime it’s called.
