I'm running Mach3 and using Sheetcam to create the GCODE. Anyway, I do have the system working overall pretty well. I would like to find a spot that has good tool settings for my setup though. I do have a recurring problem of the torch occassionally staying too high above the cut and not piercing until I stick a piece of metal in the arc, but most of my settings seem to be working pretty well. I have it down now to the point that I can cut anything that I create in Corel myself and dxfs that I get from some locations. I've run through a ton of problems over the last several months (mostly because I didn't understand what was going on, lol). I have a Plasmaroute 4x8 blaze table with a Thermal Dynamics A60 Cutmaster plasma torch.
First step is to read a simple 9V battery connected to the THCAD, until this works reading the cutting voltage is a dream.Hello, first of all, thank you in advance for your help (and for understanding that I'm a newbie who has spent a ton of hours trying to research this and figure it out before asking here).
#AUTOCAD TO SHEETCAM TNG MANUAL#
Read the THCAD manual all the offset and scaling instructions are there. There are several users here that have working systems as well and PCW that can help. What part of getting your THCAD-10 going isn't working? It should be easy on any newer Hypertherm box. Les is really good at looking after SheetCam problems.
#AUTOCAD TO SHEETCAM TNG CODE#
Again it is important that we see the code you are using. First for trouble shooting help you really need to post the text of the PP you are trying to use and the problematic code it generated. Did it run ok? If so you now have machine and example gcode running to compare to the SheetCam generated code. Now turn on your plasma power supply and try 5 or so test cuts in a row using your hand generated code, did they work ok? If not what was the failure? Now modify your hand coded simple line cutting program to have 5 separate lines and run. While doing this look at your GUI does the Z DRO value make sense for the moves you just made? Once this is all working, you may need to adjust gcode, and actual subroutines to get it working correctly on your equipment. With the plasma power supply off (you don't want the torch to fire!) verify that it is working correctly, MEASURE the pierce height and the cut height and make sure they are as set. You also may wish to rewrite them leaving out the o sub and o endsub lines and see if the resulting code will load without errors, to use as actual subroutines you will need to add the lines back in. Run all subroutines first from MDI to verify they work. Then hand write a simple gcode file that cuts a single straight line.
We need to see your actual copies! Are you using any user generated components? If so please post the source here. Please Log in or Create an account to join the conversation. We still do not have the THCAD-10 functional.I may need to ask for some guidance on the THC setup on another subsequent post, but I would like to get some resolve to this situation first.Īny suggestions or comments will be appreciated. Next is the subroutine (also developed by JT) which is called for touch-offs, pierce height, starting torch, etc.This sub has only been modified in the switch hysteresis (had to increase to 0.23" based upon machine design) and when using this sub when importing the created G-code into LinuxCNC the objects to be cut by the torch when viewed from any view except the Z top view appear on different layers.When doing the actual cut it all works okay, but I get an error message box stating that the code exceeds minimum Z limits when there are more than 3 cuts to be done, do you want to proceed anyway.Clicking yes starts the cutting process and completes properly.įrom within the subroutine code I commented out the G92 setting the Z to zero, by doing that when viewing the objects to be cut in all the various views all objects appear on the same elevation.I have tested this without doing actual cutting and it seems to go through all processes properly, but I am a little nervous about running it this way.Īs a work-around I have envisioned setting the Z limits in the ini to a larger number to avoid the error from appearing and setting the default view to Z (top view) while leaving the G92 code active in the subroutine. We are using SheetCAM TNG for G-code generation.The post processor we use in SheetCAM is the post developed by John Thornton.We have made no changes to his post with one minor exception of raising the Z torch upon completion of the final cut (next to the last line of code) instead of sending the torch to Z0.For all intents and purposes this works perfectly. We have more information now that we have had time to use the machine and evaluate what is going on.To further clarify the actual machine setup I provide the following: There is no loss of steps in Z.You are correct that the issue seems to lie in software.
0 kommentar(er)
