I have set the tool setter up and seems to work fine after homing the machine. Followed the instructions on the Mitchells Woodwork LLC youtube. Setup a project with basic text v cut and clearing. So bit #1 DCS bit and #5 V bit. Set in tool options in the machine.
Started project and it did the circles using the DCS bit then prompted me to the V bit. Swapped out and didnt turn on spindle then proceeded to continue without using the tool setter so I hit stop before it started again.
Not sure what is going wrong with these settings.
Also, whenever I use the vcarve in it puts the drill down circles, not sure what that is about.
I don’t have an ATC and run jobs with 2 -3 tools and really like having the tool setter, don’t know how I got along without it for so long, had no issues setting it up and working.
Ugly Dog Workshop has a good video on them as well as Mitchells.
Pat
I’d like to draw attention back to the poster’s question. There are several users here that can not get the tool setter to work. Some of us have even smashed their tool setters and there is CLEARLY a lot of confusion out there. The videos that everyone keeps referencing, as well as a lot of posts on this forum contain conflicting info. Also there is quite a lot of misuse of definitions. If the videos led you to a positive outcome…great. But that doesn’t solve the problem for us! We don’t need another suggestion to watch the video!
Perhaps if ONEFINITY would recognize that this is a fairly common issue, and provide some CLEAR, CONCISE information, instead of relying on youtubers to provide half baked tutorials for their product support.
A bit harsh on the youtubers and i see forums as a community for sharing, which folk are trying to do and, in this instance, respondents are responding to the original posters question.
An interesting point though with respect to OEMs. But would the question be best pointed to masso rather than onefinity?
Tool setter works great as long as you program it correctly and use masso accepted tool numbers in your CAD. Before atc i saved my files with multiple tools and tool paths without issue.
Thanks, I may play with this on a slow weekend. I figured it works, just needs some specific programming which I could not easly find in the tutorials. Onefinity is new to me as well as Carvco so its learning process. VCarve Pro seems more understandable to me and think I may just go with that going forward. At least I can manage my tools and create my baseline on tool/material customizations.
I have a similar problem but it appears to be intermittent. I have an Elite Journeyman and started using a tool setter about a month ago. I am running FreeCad 0.21.1
For many runs, the tool setter worked just fine for me to manually change tools between cuts. Typically, I have 3 - 4 cuts per file with two tool changes.
After several measurement changes to the file I have been using (e.g. changes in depth of cut and offset) I am finding that my machine makes the first profile cut properly, then stops the spindle briefly, before it starts up again before I have a chance to change from a down-cut bit to a v-bit. Twice now, it has made the second pass without the correct tool, which of course messes up my piece. And, of course, it is a safety issue as well. I am pasting in my gcode below and would value your advice.
The issue occurs after the line: “(begin operation: Whiteside_60_degree006)”
What baffles me is that the same exact code is used again for the second chage back to the original bit, and it works perfectly. BTW, I have turned off the Masso controller, re-zeroed, and reinstalled the file several times. It keeps happening. Is there something in the code I am missing?
cheers,
jrg
Thanks, I will try that. The KineticNCBeamicron2 processor wrote the Gcode incorrectly. I’ve seen this concern on a video, but I thought it had to do with an automatic tool setter rather than a manual operation. Since it works most of the time, I expect there is some condition that confuses it.
I’ll give it a try and report back to let you know.
BTW, for those of you who are having trouble destroying your tool setter. I think I may have figured out what is happening. I noticed that when I put in a new bit, it crashed into the tool setter, but I was lucky because it was not by much. I noticed that when I installed the next tool it paused as it was supposed to before touching the sensor. I believe that I had not inserted my initial tool far enough into the collet and the normal pause range was negated by the length of the tool.
It is possible that if you have had your bit crash into your tool setter, you may need more offset for the slow-down function to test the tool length or you need to make sure the tool is higher in the collet so the setter process works correctly. Not sure if this is the solution, but it works for me so far.
cheers,
jrg
Bob,
Yes, thanks. I changed the setting for safe Z height in the Auto Tool tab of General Settings. Also, I got my son to help me edit the KineticNCBeamicron2 processor I use to output gcode in FreeCad software to switch the tool code from
M09M6 T2
to M09T2 M6.
I am posting the edited Python file here if others want to use it. I had to Zip it for the forum to allow the upload. There was only one line change. My son moved the M6 code down in the script so it was added in the proper order.
cheers,
jrg
Initial location for "outstring.append (command) at line 352
new location for "outstring.append (command) at line 410
