Hello Guest it is March 28, 2024, 02:55:53 PM

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

0 Members and 1 Guest are viewing this topic.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
1st pierce is longer...
« on: August 13, 2014, 10:35:26 AM »
I am using my plasma torch to make marks for drilling on a job, it has 6 marks on it. It works very well at low power setting and a 0.1s pierce delay. After the piercings I have added a pause in the code so I can up the power and make the following cuts as normal.

However, at the start of each run, the first pierce is always longer, maybe three or four times longer than the rest.

Is there any reason for this in Mach3, I have checked the code and each pierce is identical in duration?

Maybe a setting needs tweaking?

Thanks

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #1 on: August 14, 2014, 07:26:14 AM »
No-one else notice this??

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #2 on: August 15, 2014, 03:47:41 AM »
Can't say I've seen this - post your gcode and the contents of your M3 and M5 macros.
« Last Edit: August 15, 2014, 04:07:46 AM by stirling »

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #3 on: August 15, 2014, 04:15:19 AM »
Thanks

Files below

Dave

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #4 on: August 15, 2014, 07:53:03 AM »
Nope - they're consistent here. Not accurate - but consistent.

I've never found G4 to be particularly accurate with small values. Your 0.1s actually gives 0.73s. HOWEVER - some of that is down to the delay of executing M3 and M5 because your M3 uses doSpinCW and presumably your M5 uses doSpinStop (you posted M4 rather than M5 so that's a guess). I replace these with direct signal activation/deactivation which makes the macros faster. That won't do anything for inconsistency though - don't know why your seeing that.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #5 on: August 15, 2014, 08:13:51 AM »
Hmm, that's odd then,

Where or how does the direct activation code go, is it just placed into the M3\4\5 macros or somewhere else?

Is it just a matter of changing the macro's to this style --- ActivateSignal(Output1) & DeActivateSignal(Output1) ????

I will also take the THC completely out of the loop, just in case that is causing a variation and try that.

Would make sense to replace the M codes with direct signals if you could give a little guidance please.


Many thanks for your time
« Last Edit: August 15, 2014, 08:24:01 AM by Davek0974 »

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #6 on: August 15, 2014, 09:19:25 AM »
Is it just a matter of changing the macro's to this style --- ActivateSignal(Output1) & DeActivateSignal(Output1) ????

You got it.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #7 on: August 15, 2014, 09:23:29 AM »
Thanks, thats a lot snappier now  :)

As it means my code is all wrong now (pierce too short) was there a known delay inherent in the M3\4\5 macros that I could simply add to my code or was it just a code delay of unknown length???



Dave
« Last Edit: August 15, 2014, 09:32:47 AM by Davek0974 »

Offline stirling

*
  • *
  •  2,188 2,188
  • UK
    • View Profile
    • www.razordance.co.uk
Re: 1st pierce is longer...
« Reply #8 on: August 15, 2014, 10:48:05 AM »
Running your code here, the time between the M3 activating and the M5 deactivating is:

1.73 sec using doSpinCW and doSpinStop and 0.32 sec using activate/deativate.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: 1st pierce is longer...
« Reply #9 on: August 15, 2014, 03:34:13 PM »
Thanks for the info