Hello Guest it is March 28, 2024, 07:57:00 PM

Author Topic: 1st pierce is longer...  (Read 22350 times)

0 Members and 1 Guest are viewing this topic.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #40 on: September 09, 2014, 04:30:48 AM »
:) :)

Ok, I think I see it now, nothing happens until we get arcok.

Now, looking at the issue then, what could cause the variation?

There definitely IS a variation and the only difference is the post-flow air being on or off.

The response is the difference between getting a solid pulse of the torch OR not getting enough signal to even trigger the torch.

Hang on a minute, looking at that last sentence, i was not even getting an arc on the latter part of that test as mach was not triggering the relays long enough to do it - straight M03-M05 is too fast UNLESS its the first trigger is with air OFF.

Now i'm really confused ;)

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #41 on: September 09, 2014, 04:42:04 AM »
Now I KNOW you're taking the piss.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #42 on: September 09, 2014, 04:47:28 AM »
Sorry but I'm not, obviously I am not seeing the point and I apologise for having a high specific gravity ;)

I ran a test - four pierces in a row, no delay between M03 & M05

The first pierce worked perfectly, the last ones did not even get to fire the torch as the signal duration was too short, I'm not even sure if the relay clicked.

Arcok could not even come into the equation for the last ones as the torch did not fire.

Please explain the reasoning.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #43 on: September 09, 2014, 03:05:17 PM »
Going back a few posts, there was mention of a small bug in Mach that made waiting for arcok difficult, if this is the point I am missing then I get it - it does not wait as it should.

I'm probably still wrong. :(

So......why is the first one always longer?

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #44 on: September 10, 2014, 04:58:33 AM »
Going back a few posts, there was mention of a small bug in Mach that made waiting for arcok difficult, if this is the point I am missing then I get it - it does not wait as it should.

hallelujah - (actually no one said difficult - you made that up).

So now go back and READ this thread again - or at least posts #31 to #39. Notice post #37 ?

Then this time, read ALL (not just the first page) of the thread YOU linked to in post #13 and maybe look at my first comment about that link in post #17.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #45 on: September 10, 2014, 05:12:07 AM »
***Insert facepalm smiley here***

D'oh!

Right, I'm on the ball now, i think :)

To be honest, in that linked thread, it comes up as an archived one i think in a format thats hard to follow, i didnt even notice there was more than one page before!

Anyway, is it worth my trying this for fun or has it later been proved fruitless....

Do While Not isActive(THCON)
   x = x + 1
   sleep 1
   If x = 3000 then
      MsgBox("OK To Move Timed Out")
      code "M30"
      Exit Do
   End If
Loop

Inside M3 after the DoSpin()

Also, once its configured, is ArcOk ALWAYS present or does it disappear when THC is turned off?


Any views or should i just go back to bed;)

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #46 on: September 10, 2014, 08:03:56 AM »
Well, I've tried it and yes, consistency CAN be achieved if you wait for the ArcOk signal (if only someone had said that earlier ;) ;) )

Using the code above inside the M03 macro means that even without a G04 P0.?? dwell, you can mark predictable points on the sheet without piercing through.

But as suspected, this now means you can't run a job if the torch is turned off - I do this a lot with a new job file to test the layout etc, just a dummy run through.
Also when using the CandCNC MP3000 stuff you can have a tool defined as no THC, this also upsets the action of this code.

Here's what i would do if only i knew how..

Add an LED and screen button titled "Dry Run" or something similar, the button would flip the LED on or off.
Inside the M03 macro the status of this LED would be tested and if off then none of the M03 code would run - no torch fire etc.
If on then the M03 would act as it is at present - fire the torch then wait etc.

Adding the button and LED is OK but how to toggle the LED state is unknown by me at present.
Anyone care to chip in with some code? :)

Of course, if anyone has a better version then I'd love to see it but as it is i think the code above fixes 99% of the issue.
« Last Edit: September 10, 2014, 08:05:29 AM by Davek0974 »

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #47 on: September 10, 2014, 08:52:34 AM »
Got it, I think...

Put a VB button on the screen titled "Dry Run" or similar and an LED, i called mine 2244.
in the button code...

If GetUserLed(2244) then
setuserled(2244,0)
else
setuserled(2244,1)
end if

That toggles the Led on and off

In the M03 macro:-

If getuserled(2244)=0 then
dospincw()
Do While Not isActive(THCON)
x = x + 1
sleep 1
If x = 3000 then
MsgBox("OK To Move Timed Out")
code "M30"
Exit Do
End If
Loop
end if

That stops all action from M03 if the "Dry Run" LED is on.

I'm not sure of any pitfalls in this code but it seems to do what i want.
Any views?

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #48 on: September 10, 2014, 09:21:00 AM »
So progress...<phew>

If it's all working as you'd like then great - however, instead of your LED monitoring etc. maybe you could have just put a block delete on your M3 calls? Then just turn block delete on when you want to dry run?

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #49 on: September 10, 2014, 09:28:23 AM »
I'm all for trying different ways, how does a block delete work?

I gather that would then me reloading the code for the real run?

Interesting stuff.

Can you see any issues with this M03 edit??

Thanks