![]() | |
| Home Page | Mark Forums Read | Today's Posts | My Replies | Classifieds | Reviews | Photo Gallery | Web Links | Share Files | Advertise With Us | Ad List |
| |||||||
| Mach Software (ArtSoft software) Discuss Mach 1 , 2 and the new Mach3 here NC software here! |
| This forum is sponsored by: |
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
| ||||
| ||||
I have asked on the yahoo forum also, but hoping someone here may also have some insight into my toolchanging issue. If my second tool is longer than the first, it crashes into the part. The first tool at a programs beginning always works fine. It seems the second tool height does not get activated in Mach in time. Heres my toolchange posting format, should I reorder the Txx and M06? N000186 G49 N000187 (END TOOL) N000188 T2 M06 (.342 END MILL) N000189 G90 G80 G40 G43 H2 N000190 G00 Z0.25 N000191 S2197 M03 N000192 G00 X-0.7705 Y0.6532 Z0.25 N000193 Z0.1 And here are my macros, which I am beginning to suspect: (start)........ tool = GetSelectedTool() x = GetToolChangeStart( 0 ) y = GetToolChangeStart( 1 ) z = GetToolChangeStart( 2 ) SafeZ = GetSafeZ() if SafeZ > z then StraightTraverse x, y, SafeZ SetCurrentTool( tool ) (end)........... x = GetToolChangeStart( 0 ) y = GetToolChangeStart( 1 ) z = GetToolChangeStart( 2 ) SafeZ = GetSafeZ() if SafeZ > z then StraightTraverse x, y, SafeZ StraightFeed x, y, z So - could I add a line to activate the G43 somewhere in the M6end macro? Or should I post the G43 on the toolchange line 188 in my example? Thanks Scott |
|
#2
| ||||
| ||||
| Have you watched this video? http://www.machsupport.com/ToolChange/Tool_Change.html On the Mach site? ----------------------------------------------------------------------------------------------------------- You might need to add this code between your axis moves, so that it completes the move of the axis (first) then moves on to the next code.
|
|
#3
| ||||
| ||||
| How many tools are in your ATC? Is your cnc machine diy? I think you would be better off, to take the code from that video ( http://www.machsupport.com/ToolChange/Tool_Change.html ) and modify it for your machine, looks like a good start. I don't see in your code where you swap the old tool, for the new tool. I think the Mach program is thinking that the same tool is in the spindle. That could be why it's crashing the 2nd tool. . |
|
#4
| ||||
| ||||
| N000188 T2 M06 (.342 END MILL) I haven't watched the video, but you may want to use a G43 H2 for the tool length offset.
__________________ Gerry Mach3 2010 Screenset http://home.comcast.net/~cncwoodworker/2010.html (Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management) |
|
#5
| ||||
| ||||
Ger21, I meant I dont see it in the Macro, the g-code tells the macro what tool to select, his macro isn't switching the Mach program. Looks like the control thinks the tool number is the same tool (just in a different location on the ATC) The macro is supposed to be doing all the work, T2 is just the tool to pick out of the macro. I copied the code from the video, they said it was on the Mach site, (I couldn't find it). Anyway here is the code from the video. The code has 8 tool positions.
|
| Sponsored Links |
|
#6
| ||||
| ||||
| Oh - no ATC. But you guys may be on to something. I notice when I put the second tool in, the control does, like you say, still think the prior tool is in. So, the second tool goes down (and crashes if it is longer). If the second tool is shorter, it works, because the G43 seems to be getting applied later than it should be........... |
|
#7
| ||||
| ||||
| The more I look at the Macro (standard Mach macro), it does look like it doesn't tell the control there is a new tool in the spindle, and it drives back to z safe with the new tool, before it gets the G43 from the program. Is this it? If so, how can I add the G43 to the macro? Thanks. |
|
#8
| |||
| |||
| I happen to see you were on line here and read your question. i would tend to agree with ger21 however, the problem you describe sounds like a previouse tool length offset is not beeing cancelled when you pick up the new tool. I used to have a K&T Data Mill that would do the same thing if you didn't call the tool length offset 0.0 before calling up the next tool. this was a big machine and the crashes were dramatic. Another peculair thing about that set up was weather to add or subtract the number. It's been awhile but it went somthing like, if the first tool was 5" long and that was set as Z zreo and the next tool was shorter then the length offset was put in the programe as a positive?? Think about it, maybe that is what is going on. Also, do you use the same "H" number for all your tools? I believe that if you call a different H with the same T number (T1 H1, T1 H2,...) you can use different length offsets for the same tool. I'm not as familiar with G code as I should be so don't hold me to this. |
|
#9
| |||
| |||
| Just so you know, your not alone, I've been having the same trouble and still can't find an answer to fix it yet. I Set Z with the longest bit, they set tool 1, tool 2 and tool 3. I can verify the offset but number and by running "goto Z" for each tool. All is good until i run the g code. Then tool 1 stops somewhere above the work piece. and the only tool that touches the work piece is the tool used to set Z zero. If you use a shorter bit to set zero, then all the other bits crash (did that twice). Let me know if you find the solution. I'll post back as soon as I figure it out. |
|
#10
| |||
| |||
| bbuonomo, consider that on most controles the tool data page and the fixture offset page are two different G codes in the program, are you sure you are defineing the fixture/work location with the correct G code? Also do you need to "home" the nachine before you set tools or find the work location? I know that some machines I've run,would run w/o homing first but wouldn't know ware they were, some won't start w/o homing first, some pick up right ware they left off. Examin your situation carefully I'm sure it must be somthing subtle that you're missingin your procedure...? merl |
| Sponsored Links |
|
#11
| |||
| |||
| i don't have a x.y home, but I can home Z. I turn on PC, load Mach3, turn on machine (bridgeport Series 1 CNC connected to a breakoutboard that plugs into the PC). The machine has no inteligence, just stepper motors and a few limit switches. Spindle control is manual. I load the g code into mach3, i find Y and Y zero positions and zero them in mach3. Then I do my tool offsets. I insert the longest tool, use that to find Z Zero (top of workpiece). Then I type in the tool number for that tool, set offset (which is now 0.00 because it is equal to Z zero). Then I reference all home, insert tool 1, type tool 1 into tool number field, hit enter, jog tool down, hit set tool offset, reference all zero and then goto Z to test offset. That works. I do the same thing with tool 2. Test goto Z with all tools everything is good. Hit cycle start, mach3 stops for tool change,i make sure correct bit is in spindle, hit cycle start and then tool 1 offset is now down at workpiece. Program operates above the part. So I hit stop, reference all home and when I run goto Z for each tool, all the tools are above the table. Except the tool that was used to set Z zero, that tool will still touch the top of the work piece. I'm sure it is something proceedural or a very silly setting in Mach3 that I didn't see or know to select. Attached is the gcode for teh 36 tooth sproeck that I'm trying to cut. The code runs perfectly as long as I run 1 tool at a time. 4 tools as 4 seperate processes. any help is gretaly appreciated. |
|
#12
| ||||
| ||||
| My WAG would be that the tool change macro is not responsible for calling the length offset. As Merl said, put a T0 and/or G43 H0 in your gcode before the tool change, as this should cancel an existing offset. This would be a precaution in case there is some kind of mixup in how the difference between length offsets is being handled in MACH. Also, try putting the call for the length offset on a line by itself. Include a motion command (G00) with it. G00 G43 H
__________________ First you get good, then you get fast. Then grouchiness sets in. (Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management) Last edited by HuFlungDung; 11-21-2006 at 11:13 PM. Reason: typo |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
| |