Hello everyone - I have reached the point of asking for HELP!

I am new to this, but here we go.

Working with Mach3 BladeRunner AIO, 620-4 axes / motors. The Plasma Gantry is Precision 4 X 4 with
floating head. Using SheetCam with the POSTs that Tom sent with the package configuration (for
THC: MP1000-THC-Z ref).
I have it ready and working. Movement direction and display are correct and adjusted.

I drew a simple 4-line test cut and tried to execute it. It made the quick movement to S-1, it made the
drilling, the torch went out, and Z rose about half an inch and EVERYTHING stopped, it
stopped at: NO110 G28.1 Z0.50. I have tried to start from the beginning several times and I get the same
result.
I also tried another simple line drawing with the same result: it stops at: G28.1 Z0.50. Z rises
approximately half an inch, the torch stops cutting, the movement stops.
MACH NO enters RESET.

More readings (rereading that is) and research here ... I found that I had to set the scrolling
from the switch Z - OOPS. In Sheetcam, I followed the instructions from a post here. Click on the 'V'
(publication variable) and write: switchoffset and the figure / number .144 that I came up with and is in
inches (Ref Z and zero, rise until a paper slides under it).
BUT ... when I enter this in the 'Publication Variable' and then run the publication, I receive a
WARNING: No immersion rate and No feed rate.

He executed the POST anyway on the same line drawing and the machine reacts in the same way:
It stops after drilling, rises about half an inch and stops. MACH does not reset.
only stops.

Suggestions on what path to take ... what to check?

I got pretty excited for about ... 3 seconds when I pressed RUN and it was because of that first
piercing.

Thank you people!

Similar threads:

sheetcam
SheetCam and EMC
sheetcam
Problemsheetcam!
SheetCAM?

With all my reading on this site, I made a little mistake. The movement stops at: N0160 M03. I will try to include
the POST. Does this seem correct?

N0000 (File name: TestCut11.tap)

N0010 (Postprocessor: MP1000-THC-ZRef.scpost)
N0020 (Date: 8/11/2012)
N0030 G20 (Units: inches)
N0040 G53 G90 G40
N0050 F1
N0060 (Piece: TestCut1)
N0070 (Process: External displacement, Layer 1, T1: Plasma, cutting of 0.0591 inches)
N0080 M06 T1 F90 (Plasma, cutting of 0.0591 inches)
N0090 G00 Z0.5000
N0100 X0.5321 Y7.9823
N0110 G28.1 Z0.50
N0120 G92 Z0.0
N0130 G00 Z0.0900
N0140 G92 Z0.0
N0150 G00 Z0.1181
N0160 M03
N0170 G04 P0.5
N0180 G01 Z0.0591 F3.937 N0.550 G04 P04 P0450
N0190 X0.5493 Y0.0000 F90.0
N0200 M05
N0210 G00 Z0.5000
N0220 X1.0299 Y8.0338
N0230 Z0.1181
N0240 M03
N0250 G04
P0.5 N0260 G01 Z0.0591 F3.937
N0270 Y0.0515 F90
N0280 M05
N0290 G00 Z0.5000
N0300 X1.5449 Y8.0338
N0310 G28.1 Z0.50
N0320 G92 Z0.0
N0330 G00 Z0.0900
N0340 G92 Z0.0
N0350 G00 Z0.1181
N0360 M03
N0370 N
G0480 P0.5 Z0.0591 F3.937
N0390 X1.5106 Y0.0000 F90.0
N0400 M05
N0410 G00 Z0.5000
N0420 X0.0000 Y8.1024
N0430 Z0.1181
N0440 M03

N0460 G01 Z0.0591 F3.937

N0470 X0.0171 Y0.0344 F90.0
N0480 M05
N0490 G00 Z0.5000
N0500 X0.0000 Y0.0000
N0510 M05 M30

It's just a simple test line cut. Is more information needed?

In MACH, in config / safe Z ... should I let MACH or JOB make the offer? It has .5 as a measure. I just noticed.
This publication came with Sheetcam. Tom is 'mp3000' (mp1000 verses). Could this be the problem?
Working on the terminology ... HERE IS the POST processor ... the other was g-code. I thought it would be better to show
also WHAT processor was being used. A snapshot.

function OnAbout (event)

ctrl = event: GetTextCtrl ()
Plasma MP1000-THC -ZRef post-processor
Use with floating head (auto touch off) ONLY
Modal G codes and coordinates
Comments between (and)
M03 / M05 turn on / off the torch
Incremental IJ - set in mach3
It refers to the torch at the beginning of the cut and every 500 mm of movement from
then
Designed for use with Mach3 and CandCNC MP1000-THC and Touch-n-Go floating head
end

Publication variables:

--refdistance sets the distance between each reference (the default value is 500 mm)
--switchoffset - sets the amount of net switch offset (measured switch offset
real on his table)
--zrefslowdown - sets the distance that Z uses the reference speed in the triggering. If it is larger than
Rapid Height, USA Rapid Height

modified on 10/05/07 by Tom Caudle

Based on the

function plasma1.post OnInit ()

big arcs = 1 - cos of arc segments together
minArcSize = 0.05 --arcs más pequeños que esto se convierten en movimientos

post.SetCommentChars ("()", "[]") - make sure that (and) the characters do not appear in the system text
(File Name:
(Postprocessor: postName)
(Date:
if (scale == metric) then
G21 (Units: Metric) --metric mode
else
G20 (Units: Inches) --inch mode
end
G53 G90 G40 F1
--NOTE: The numbers of the variables below are in MM and are converted to INCHES by the factor of
scale
dist
9999999 refdistance = 500 * scale
zrefslowdown = 12.7 * scale -
Put the compensation value of the switch here
switchoffset = .090
lastz = 0
if (zrefslowdown > safeZ * scale) then
safeZ * scale
end
end

the offset of the switch was never touched, it came that way. I tried using Sheetcam 'Post Variable' unsuccessfully. Can I
Should I enter this figure as MM or inches? I am using inches in MACH and SheetCam.

Words of wisdom and experience please!

Alright, I'm not an expert by any means. This is how I do it. First, to edit the post-processor, go
to the option (in Sheetcam), machine, post-processor. Choose your publication then, Edit publication. Scroll down
Down in the editor, in: function, go to 'change offset' and change the 'number' only as per your needs.
Then 'save' the file. redo to ensure it changes.
It does not set the feed rate and immersion in the publication. It is configured first within Sheetcam.
when configuring a new cutting tool, then run the post after choosing that tool
cut and execute the route routine.
I have also had my torch pins "up" and "down" inverted in Mach. I could try changing them to
see if the torch now moves down instead of up to reach its cutoff height and voltage
suitable cut. Wait by the reset button in case you want to push through the material.
When you turn on the THC, does the Torch Active button on Mach turn on?

If it still works and no one else can help you, send me an email and I will give you my number.
phone and maybe we can resolve it over the phone. I created many of my own problems when DynaCNC was
sank.

This is how my Gcode (DYNA6KTHC publication) looks very similar:

N0000 (File name: ROUND BUCKY FACE.tap)
N0010 (Postprocessor: D4KATHC2.scpost)
N0020 (Date: 04/29/2010)
N0030 G20 (Units: Inches)
N0040 G53 G90 G40
N0050 F1
N0060 (Part: ROUND BUCKY FACE)
N0070 (Process: Plasma, External displacement, LAYER_1, T1: CUTMASTER 40 AMP)
N0080 M06 T1 F190 (CUTMASTER 40 AMP)
N0090 G00 Z0.7500
N0100 X-0.5647 .3138
N0110 Z0.2000
N0120 G28.1 Z0.12
N0130 G92 Z0.0
N0140 G00 Z0.2500
N0150 G92 Z0.0
N0160 G00 Z0.2000
N0170 M03
N0180 G04
P0.5 N0190 G01 Z0.1900 F30
N0200 X-0.5924 Y0.2606 F190
N0210 G02 X-1.2179 Y0.6694 I1.7515 J3.3625
N0220 X-2.1755 Y1.5034 I10.2575 J12.7459
N0230 G03 X-3.2189 Y2.2426 I-3.1664 J-3.3632

Good luck,
Mike

Sheetcam and code before M03Published by pordeilyn

How do I manage to introduce a code before M03 in Sheetcam, I already tried 'code snippet' or code fragment.
and I don't know how to modify the post-processor.. I use the mach3 plasma...!!!

the code I would like to introduce is the following

after the m03

G04 P0.4 (PAUSE)
G00 Z1.5 (Go to 1.5mm up)
G01 Z0.5 F100 (Lower Z to 1.5mm at defined speed... check that it is the G31 code for this)

My torch ignites because of HF... and I would like to create the electric arc and then rise and come drilling.
little by little... so it doesn't damage the consumables so quickly.... I haven't tried the ramp options or the other one..
someone help me...

G04 P0.4 (PAUSE)

G00 Z1.5 (Go to 1.5mm up)
G01 Z0.5 F100 (Lower Z to 1.5mm with defined speed... check that it is the g31 code for this)

with G00 Z0 it should save the safety distance

And with G01 Z0.5, it would lower the axis to 0.5, check that the line you have G00 Z1.5 recognizes that you want to raise it.
If you cannot assign a negative value Z-1.5
I have been looking at some post-processors, and I was wondering regarding the plasma and the THC which one
It would be the sequence of function calls by SheetCam, as it seems that some post-processors appear
to call some events differently and, therefore, the events are within different functions.

Is there a manual / flowchart somewhere?

It is mainly because I see that some THC post-processors are not using the cutHeight variable, despite
of using the variable pierceHeight, so I am not sure if they are falling to cutHeight through OnMove
() or possibly even OnArc () (as the DHTC postprocessor does).

When is OnPenDown() called, is it every time the Z axis moves down, or only at the beginning?

Therefore, in a JetOperation using a PlasmaTool, what would be the sequence of events ...
OnRapid () - move to the start of the cutting operation
OnPenDown () - reference the Z axis, fire the torch, allow drilling delay and drop to the height
of cut (in PlungeRate)
OnMove () - cut the forward speed
...

Oh, is it

OnRapid () - move to the start of the cutting operation

OnPenDown () - refer to the Z axis, turn on the torch, allow the delay
drilling and lowering to cutting height OnMove() - lowering to cutting height (in PlungeRate)
OnMove () - cut the advance speed
...

I am trying to figure out what triggers the 'OnPenDown()', it is called once at the beginning of the cut, followed by
from an OnMove() which is the X and Y movement, or the fall to cutheight is also captured in this OnPenDown(), or
it has its own OnMove ()

Sorry for the long post, I hope it makes sense, some guidance on the sequence of function calls.

Thank you

Rob

In case you are wondering what I am adding in the voltage + THC delay configuration to store
directly with the tool and then send to the THC in the tool change [what I have discovered and
I am happy with], I also have a pneumatic engraver in my machine that works with a couple of relays, happy
With all that, I just try to learn something here and understand what others have done in a bit more detail.
thank you for your time).
Top part
 The Newell

Site Administrator

Publications2591
Registered: Thu May 11, 2006 8:12 PM

Citar

SendforThe NewellApril 26, 2016 5:07 PM

The sequence is:

OnRapid () Move to the X, Y coordinates of the cut
OnRapid () Move down to the height of
drilling OnPenDown() Reference, turn on the torch, etc.
OnMove() Move down to cut the height at the immersion speed
OnMove / OnArc ... cut shape.

OnPenDown occurs every time the torch moves down at the beginning of a cut. For a post
very minimalist, just needs to light the torch on OnPenDown.

Looking back, it would have been better if OnPenDown had fired before the movement to pierce the height.
the problem is that if I change it now, it could break quite a few post-processors that depend on the behavior
actual.
Top part

robertspark

Publicaciones: 163
Registered: Thu Feb 26, 2015 12:11 am

near Liverpool, England

Citar

SendforrobertsparkApril 26, 2016 7:30 PM

Lель, thank you very much for the information, it's great, now I understand a little more.

No, I wouldn't change anything, but now explain why the onmove() functions look the way they do with the movement.
of the z axis.

For me, it is a hobby, and I'm happy to play and learn post-processors, lua, m3, m4, etc.

Thank you for taking the time,

Rob