Hello Guest it is September 21, 2019, 02:21:30 AM

Author Topic: Plasma Consumable Tracking  (Read 26014 times)

0 Members and 1 Guest are viewing this topic.

Re: Plasma Consumable Tracking
« Reply #80 on: November 01, 2012, 10:00:59 PM »
I am running normally just with the torch off. Not simulation. I figured that would be the best real world test. I have tried with the torch active and it made no difference.

I tried lowering kernel speed, that made no difference. I tried evoking a modified 3007 from the g-code and that didn't work any better either. But I'll keep messing with it.

If you have any brainy ideas, let me know and I'll try it.

Thanks

GL

Offline BR549

*
  •  6,898 6,898
    • View Profile
Re: Plasma Consumable Tracking
« Reply #81 on: November 01, 2012, 10:49:17 PM »
What OS and version of MACh are you running?

(;-) TP
Re: Plasma Consumable Tracking
« Reply #82 on: November 01, 2012, 10:52:10 PM »
Windows XP Pro Service Pack 2, Mach 3 Ver, R3.043.066

GL
« Last Edit: November 01, 2012, 10:54:41 PM by scbrniddvl »
Re: Plasma Consumable Tracking
« Reply #83 on: November 01, 2012, 11:10:07 PM »
A week or so ago
i ran into a problem with the newer versions of SheetCam, Versions 4.0.16 and .21 weer not entering the switchoffset data from the post processor to the g-code. I went back to 4.0.14 and it worked fine.
Go figure. Strangeness. ???

Gl
Re: Plasma Consumable Tracking
« Reply #84 on: November 02, 2012, 12:53:04 PM »
I have a question. In the mod for the post processor for preview is this correct?

 OnPenDown()

 if  (string.find(operationName, _("Outside Offset") )) then
     post.TextDirect("o549 \n")
     post.Text (" X")
     post.Number (Sline1,"0.0000")
     post.Text(" Y")
     post.Number (Sline2,"0.0000")
     post.Eol()
   end

The post.TextDirect("o549\n")

Just looks strange.

Thanks

GL
« Last Edit: November 02, 2012, 12:54:41 PM by scbrniddvl »
Re: Plasma Consumable Tracking
« Reply #85 on: November 02, 2012, 01:14:01 PM »
This is what it looks like in the post:

N0260 (Operation: Outside Offset, Default, T1: Plasma, 0.018 inch kerf)
N0270 M05
N0280 G00 Z1.0000
N0290 X2.1858 Y-0.1858
N0300 Z0.1200
o549
N0310 X2.1858 Y-0.1858
N0320 G28.1 Z0.12
N0330 G92 Z0.0
N0340 G00 Z0.2000
N0350 G92 Z0.0
N0360 G00 Z0.1200
N0370 M03

 ???

GL
« Last Edit: November 02, 2012, 01:17:46 PM by scbrniddvl »

Offline BR549

*
  •  6,898 6,898
    • View Profile
Re: Plasma Consumable Tracking
« Reply #86 on: November 02, 2012, 01:38:33 PM »
(;-) In order to use the GOTO object the Oword it cannot HAVE a line number in front of it. SO the line in question

The post.TextDirect("o549\n") Does just that. IT writes the TEXT direct to the stack without the Line number.

That way the Oword is recognised by MACH3.


BUT something is wrong in your post as it should be inserted AFTER the M3 call so the torch will NOT light and the TOM(G28.1) will not run.

(;-) TP
Re: Plasma Consumable Tracking
« Reply #87 on: November 02, 2012, 01:52:03 PM »
I learn something new every day. ;D Ok, that was just a snippet of the post I'll fart with it. I thought I inserted it where you said in the OnPenDown section. Here is what it looks like.

function OnPenDown()
   Tpierce = (Tpierce + 1)
   if (string.find(operationName, _("Outside Offset") )) then
     post.TextDirect("o549 \n")
     post.Text (" X")
     post.Number (Sline1,"0.0000")
     post.Text(" Y")
     post.Number (Sline2,"0.0000")
     post.Eol()
   end
   if(dist >= (refdistance)) then
      dist = 0
      post.ModalText(" G28.1 Z")
      post.Number(3 * scale, "0.00")
      post.Eol()
      post.ModalText(" G92 Z0.0\n")
      post.ModalText (" G00")
      post.ModalNumber(" Z", switchoffset, "0.0000")
      post.Eol()
      post.ModalText(" G92 Z0.0\n")
      post.CancelModalNumbers()
   end
   post.ModalText (" G00")
   post.ModalNumber (" Z", pierceHeight * scale, "0.0000")
   post.Eol()
   if (preheat > 0) then
      post.Text ("\n G04 P")
      post.Number (preheat,"0.###")
      post.Eol()
   end
   post.Text ("\n M03\n")
   if (pierceDelay > 0) then
      post.Text (" G04 P")
      post.Number (pierceDelay,"0.###")
      post.Eol()
   end
end

GL

Offline BR549

*
  •  6,898 6,898
    • View Profile
Re: Plasma Consumable Tracking
« Reply #88 on: November 02, 2012, 02:01:46 PM »
Try it this way the function is added to the end of the OnPenDown() function AFTER the M3 CALL.



function OnPenDown()
   
   if(dist >= (refdistance)) then
      dist = 0
      post.ModalText(" G28.1 Z")
      post.Number(3 * scale, "0.00")
      post.Eol()
      post.ModalText(" G92 Z0.0\n")
      post.ModalText (" G00")
      post.ModalNumber(" Z", switchoffset, "0.0000")
      post.Eol()
      post.ModalText(" G92 Z0.0\n")
      post.CancelModalNumbers()
   end
   post.ModalText (" G00")
   post.ModalNumber (" Z", pierceHeight * scale, "0.0000")
   post.Eol()
   if (preheat > 0) then
      post.Text ("\n G04 P")
      post.Number (preheat,"0.###")
      post.Eol()
   end
   post.Text ("\n M03\n")
   if (pierceDelay > 0) then
      post.Text (" G04 P")
      post.Number (pierceDelay,"0.###")
      post.Eol()
   end

Tpierce = (Tpierce + 1)
   if (string.find(operationName, _("Outside Offset") )) then
     post.TextDirect("o549 \n")
     post.Text (" X")
     post.Number (Sline1,"0.0000")
     post.Text(" Y")
     post.Number (Sline2,"0.0000")
     post.Eol()
   end
end

GL
Re: Plasma Consumable Tracking
« Reply #89 on: November 02, 2012, 02:21:33 PM »
Ok, got it, works good . Any comment on my OS or Mach ver. ? Have you heard of anyone else having problem with the later Scam?


Thanks again O Master.

GL