Run GCode in mach3

[robertspark]

On the working machine...

Go >> File >> Save Toolset As.... give it a name + save it to somewhere like your desktop.

Then

Go >> Help >> Create a Support File, select all items listed + click on "Create File"
This will create a zip file with all the important settings, including you current (working) post processor.
Save that to the desktop.

Copy the zipped support file and your toolset over the the unworking machine and load in the various files (you will need to unzip the zipped folder).

toolset is added via File>> Open Toolset plus File >> Save Default Toolset.

Options >> Machine >> Post Processor Import to inport your post processor

[Plasron]

Thanks Robertspark
I will do it when I go back to my brothers house.
I’m sorry for being such a pain in the yong yang to you Robertspark, But your helpis greatly appreciated.
Ron

[robertspark]

No problem I don't mind.... If I did I wouldn't be replying

[Plasron]

On the working machine...

Go >> File >> Save Toolset As.... give it a name + save it to somewhere like your desktop.

Then

Go >> Help >> Create a Support File, select all items listed + click on "Create File"
This will create a zip file with all the important settings, including you current (working) post processor.
Save that to the desktop.

Copy the zipped support file and your toolset over the the unworking machine and load in the various files (you will need to unzip the zipped folder).

toolset is added via File>> Open Toolset plus File >> Save Default Toolset.

Options >> Machine >> Post Processor Import to inport your post processor

Thanks Robetspark the transfer went well.
Would you have a look at the attachments I'm posting, when I process a tap file, import it into Mach3 and run it, my Z axis arrow moves very slowly to the bottom and stops there, The numbers just keep running in the Z axis.
Thanks
Ron

[Plasron]

jet_tool.png

On the working machine...

Go >> File >> Save Toolset As.... give it a name + save it to somewhere like your desktop.

Then

Go >> Help >> Create a Support File, select all items listed + click on "Create File"
This will create a zip file with all the important settings, including you current (working) post processor.
Save that to the desktop.

Copy the zipped support file and your toolset over the the unworking machine and load in the various files (you will need to unzip the zipped folder).

toolset is added via File>> Open Toolset plus File >> Save Default Toolset.

Options >> Machine >> Post Processor Import to inport your post processor

Thanks Robetspark the transfer went well.
Would you have a look at the attachments I'm posting, when I process a tap file, import it into Mach3 and run it, my Z axis arrow moves very slowly to the bottom and stops there, The numbers just keep running in the Z axis.
Thanks
Ron

jet_cutting.png

[robertspark]

there is nothing apparent in those files .... plunge rate is 40ipm.....

can you post a snippet of the gcode (I don't need to see the whole thing if it's something you want to keep private just the bit that is causing the solw Z axis motion).

Is it at the touchoff.... at the plunge.... when?

it may also help if you post your mach3 profile (the XML file) so I can see what your rapid settings are for the Z.... but I'd expect that this would be higher than 40 ipm.

the machine is a dumb object.... it just does what the gcode tells it.... unless the maximum feedrates are below the gcode then it will limit it to the rapid gcode rate....

[Plasron]

there is nothing apparent in those files .... plunge rate is 40ipm.....

can you post a snippet of the gcode (I don't need to see the whole thing if it's something you want to keep private just the bit that is causing the solw Z axis motion).

Is it at the touchoff.... at the plunge.... when?

it may also help if you post your mach3 profile (the XML file) so I can see what your rapid settings are for the Z.... but I'd expect that this would be higher than 40 ipm.

the machine is a dumb object.... it just does what the gcode tells it.... unless the maximum feedrates are below the gcode then it will limit it to the rapid gcode rate....

I'm testing the cut on my computer at home in Mach3, wasn't paying any attention to torch on off was watching the Z axis arrow very slowly going down , I believe it would be plunge.
I'm not sure what you mean by posting the mach3 xml file profile.
here's a bit of code

Code: Select all

N0010 (Filename: 40 Ford.tap)
N0020 (Post processor: Mach3 plasma.scpost)
N0030 (Date: 1/5/2020)
N0040 G20 (Units: Inches)
N0050 G53 G90 G91.1 G40
N0060 F1
N0070 S500
N0080 (Part: 40 Ford)
N0090 (Operation: Inside Offset, Lines, T4: 11 Gauge)
N0100 M06 T4 F100.0  (11 Gauge)
N0110 G00 Z0.5000
N0120 X1.6290 Y3.6883
N0130 Z0.0500
N0140 M03
N0150 G04 P0.2
N0160 G01 Z0.0625 F100.0
N0170 G03 X1.8437 Y3.8506 I0.0217 J0.1944
N0180 X1.6921 Y5.1461 I-2.5714 J0.3557
N0190 M05
N0200 G00 Z0.5000
N0210 X1.5870 Y5.3634
N0220 Z0.0500
N0230 M03
N0240 G04 P0.2
N0250 G01 Z0.0625
N0260 G03 X1.2576 Y5.3003 I-0.1524 J-0.0958
N0270 M05
N0280 G00 Z0.5000
N0290 X1.1945 Y4.9289
N0300 Z0.0500
N0310 M03
N0320 G04 P0.2
N0330 G01 Z0.0625
N0340 G03 X1.4889 Y3.7654 I1.3614 J-0.2745
N0350 M05
N0360 G00 Z0.5000
N0370 X2.0496 Y3.7584
N0380 Z0.0500
N0390 M03
N0400 G04 P0.2
N0410 G01 Z0.0625

[Plasron]

Hey Robert do you think since it is an edited processor, that I may not be able to run in in Mach3 on my home computer and must run on the plasma machine only

[robertspark]

If the post processors are the same then sheetcam will output the same code if the cad files are the same, and the tools are the same and the units setting within sheetcam are the same.

If you have 2 machines with mach3.... Are the profiles on both machines the same???

Copy the profile from the working machine to the 2nd machine

It will be the XML file within the c:\mach3 folder with the same name as shown on the mach3 screenset / display

[Plasron]

If the post processors are the same then sheetcam will output the same code if the cad files are the same, and the tools are the same and the units setting within sheetcam are the same.

If you have 2 machines with mach3.... Are the profiles on both machines the same???

Copy the profile from the working machine to the 2nd machine

It will be the XML file within the c:\mach3 folder with the same name as shown on the mach3 screenset / display

Thanks Robertspark , I will check if both computers have the same settings, will have to get my brothers computer and do a side by side comparison, I will copy the profile to my computer.
Thank You
Ron

[Plasron]

Hey Robertspark
I haven’t left you hanging, I haven’t been to my brothers yet to get his computer, to do a comparison. Thanks
Ron

[robertspark]

No worries you can pm me if you want

Don't get frustrated with plasma and CNC.... It is not easy.... But it is rewarding.... If anyone finds it easy when they start out then they have been lucky and they just have not been caught out yet by something not working as it should or they they think it should plus have been lucky with their post processor spitting out workable gcode that they may not understand...

To learn something always costs money.... And a good education costs good money imho .... YouTube may appear free but maybe people just value time too cheaply..... When time starts running out for you then your value of time will rise exponentially.

[derekpittx]

Thanks for taking the time to help! 9apps cartoon hd

[acourtjester]

coming in late but from one of you posts you seem to have a problem running Mach on a computer that is not hooked to a table.
when running a G-code that looks for ( g31 or g28) touch off for the metal surface you need to activate a "Hot Key" that will trigger Mach to emulate that. This is done by going to the config menu then inputs menu then to either Z home or probe input line. Over to the right for that line there is an box for emulate change it to a green check that click on the hotkey box a small menu will pop up you can press any key on the keyboard to use as a trigger, I use the inset or print screen key. Now when running the G-code and you see the line for the Z home or probe come up and the arrow is moving down hit that key. This emulates that happening for Mach and will run the rest of the G-code until the next time it is needed.
After you have run this for testing go back and remove the hotkey so it does not interfere with normal Mach operations. Mach will not run normally with a hotkey enabled, it will override the normal input.

hot key 1.JPG