mach 3 status no tool

[NB Forrest]

I download a g-code file from sheetCam and I get the status Operation: Outside Offset, Red. No Tool. I have a tool listed in SheetCam. I am very new to all of this so please forgive me it this is a really stupid question. Why doesn't Mach 3 recognize my set up in SheetCam for tool 1?

tool 1.png (35.36 KiB) Viewed 5871 times

tool 1.png (35.36 KiB) Viewed 5871 times

[acourtjester]

It looks like you did not do the operation for the cut in SheetCam here is a g-code I just did without doing the operation action in SheetCam it is very close to yours. Another thing do you have a tool 1 red??

4 washer BBB.JPG (23.6 KiB) Viewed 5857 times

4 washer BBB.JPG (23.6 KiB) Viewed 5857 times

[NB Forrest]

Tool1 sheetCam.png (50.03 KiB) Viewed 5851 times

Tool1 sheetCam.png (50.03 KiB) Viewed 5851 times

I think I have a tool 1 but I don't know what red is referring to.
And this is what I get in Mach3

I notice the image does not show up in the mach3 display. It is just a simple circle.

[tcaudle]

hover over the RED Operation and see what it tells you. You do not have a toolpath so it won't show up in the toolpath window of MACH3 or any program.

Looks to me like you don't have a toolset loaded in SheetCAm or you did not assign one correctly to that layer in the operation

[tcaudle]

You can see from the Gcode there is nothing to cut

[acourtjester]

Ok when you see the X and the operations does not have white lettering that is an indication there is a problem with the operation. It may be you tried to do an offset and it is a open path, you then change to a on offset operation to correct it. In you image you only show one tool and it may not be complete (missing a parameter). You need to create the tools for different cutting operations. My tools are for each thickness of metal and there are different parameters for different metals. These have things like speed, amps, pierce times, pierce height, cut height, and other things. This is so when you make an cutting operation the controller know how to do it for what you are cutting. You case it did not show in Mach as SheetCam cannot complete the creation of the G-code because of the error. It may look like it did but Mach shows it did not. Do a search in YouTube about G-code creation in SheetCam that may help you see how it is done.

[djreiswig]

Or you didn't select the correct layer. Post a picture of your operation setup screen.

[NB Forrest]

[NB Forrest]

Bama layer red.png (82.9 KiB) Viewed 5794 times

Bama layer red.png (82.9 KiB) Viewed 5794 times

[acourtjester]

post your image Bama layer red,png so we can show you what to do. This is new to you and will take some instructions but like all of us you will learn.
First off when you do build a tools list remember to save it as the default toolset under the file menu drop down. Or you will not have it when you restart SheetCam, always do this when changing or adding tools.

[Joe Jones]

SHEESH! I am glad I don't have to deal with all of that cr*p!

Joe

[djreiswig]

You need to select which layer in your drawing you want the operation to apply to. The layer box is empty on your operation, so SheetCam doesn't know what you want to cut.

[adbuch]

I agree with Tom (AC) - please post your image file so we can show you how to proceed using SheetCam to create your cut paths and g-code file. Also - as djreiswig mentioned - you need to specify a layer name for your SheetCam operation.

David

[goplumcrazy]

Thank you for your help, I'm making headway but I still have a few issues. The image i load into SheetCam is what I want and it shows the proper size with respect to my table. My table x axis is 69" and my y axis is 33".

Fluer de lis SheetCam.png (51.26 KiB) Viewed 5732 times

Fluer de lis SheetCam.png (51.26 KiB) Viewed 5732 times

but when It in imported into Mach 3 it is upside down and to the upper right hand corner.

[goplumcrazy]

I did not have table display on. This is how it comes into my mach 3.

Also when I hit Cycle Start on Mach 3 my gantry uses up all of my y table and actually hits my y axis limit switch.

[adbuch]

When you import your vector file (dxf or svg) to SheetCam, there is the option to position your drawing on the table. You can experiment with positioning it at different locations in SheetCam and then see where it ends up on your Mach3 screen. Do some "dry runs" with your torch off so you can see how it will cut without actually cutting it. Also sometimes using a Sharpie Pen Holder can be useful to draw instead of cut your design - for testing.

David

[djreiswig]

No sure why it's upside down, but according to your DROs, your torch & the object is close to the origin. Do you have your torch zeroed in the correct position on your table? If you're running out of travel, then your zero must be in the wrong corner of the table.

[djreiswig]

David, in my experience, setting the location in that dialog just changed where on the material the part is dropped. You can move it anywhere on the material you want regardless of that setting.

[acourtjester]

First of all download the development version (free and more options). the attached images will help you under stand how to size your table and position added parts. How to move the parts of nesting on you table display, you manually move them with the mouse or change location with the X and Y coordinate at the bottom. After adding a new part move it manually to a new location before adding another part on top as it will be have to separate and move stacked parts. If using the coordinate at the bottom the X 0.0 is all the way to the left and Y 0.0 is all the way on the bottom.
You can also make the move lightly by increasing or decreasing the Y or X value, this allows you to neat the parts closer together.

sheetcam 1.JPG (62.62 KiB) Viewed 5716 times

sheetcam 1.JPG (62.62 KiB) Viewed 5716 times

[adbuch]

Tom - thanks for that great information! What options does the development version offer which are not contained in the latest version I am using?
Thanks,
David

[adbuch]

David, in my experience, setting the location in that dialog just changed where on the material the part is dropped. You can move it anywhere on the material you want regardless of that setting.

I agree that you can move the part anywhere on the table, but I'm pretty sure that the table location placement in SheetCam will dictate the actual plasma table location once he imports his g-code file to Mach3. Thanks!!
David

[acourtjester]

For NB what we are stating is in SheetCam you can nest your part and the lower left corner is the X and Y 0.0 for the operation plan. When loaded on the table controller where you designate X and Y 0.0 is where it will position and start that operation (G-code). Example I was cutting parts from a 8" wide 3/8" plate so my nesting in SheetCam was setup for that. Where I placed the plate on my table depended on where I positioned it and told the controller where X and Y 0.0 was. This is also handy if you are cutting on a sheet that already had parts cut from it or partial sheets.
David this is what the web states

SheetCam
https://www.sheetcam.com › downloads
SheetCam TNG Development version. This is the latest version of SheetCam. It has the newest features but also may not be as reliable as the stable version.

[djreiswig]

I set my table 0,0 to the lower left corner, then I cut parts starting at the upper right corner and move towards the lower left. This way I don't cut away my 0,0 point and can realign the sheet next time.

[adbuch]

David this is what the web states

SheetCam
https://www.sheetcam.com › downloads
SheetCam TNG Development version. This is the latest version of SheetCam. It has the newest features but also may not be as reliable as the stable version.

Thanks Tom! It looks like the difference is mostly "bug fixes". I was just wondering if there was a particular feature that you use and like with your development version that is not available with the stable version. I would also assume that as time goes on - each development version eventually becomes a stable version.

David

[acourtjester]

David since I have always used the development version, and it auto updates too I cannot say what advantage there is. When ever I had a problem with a Post Processor communication with Les has straightened them out, but don't think that would be under a bug fix. Just a correction for me to use or see what is needed. I'm not really one who burrowers deeply in to the coding, I am more of a surface searcher.