Hello Guest it is March 28, 2024, 06:10:29 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Davek0974

2301
General Mach Discussion / Re: 1st pierce is longer...
« on: September 12, 2014, 10:58:00 AM »
From a reply by Tom at CandCNC it seems that when THC is turned off in Mach, all three inputs - ArcOk, Up & Down are ignored by Mach.

That means I cannot run code without THC using my edited M03 macro (above).

Oh well, it's better as it is, at least I get predictable pierce timings now.

2302
General Mach Discussion / Re: 1st pierce is longer...
« on: September 11, 2014, 04:27:12 AM »
Question:-

If "ArcOk" is configured in ports & pins and the signal is being sent to Mach from the plasma system, is it ALWAYS present inside Mach OR does it get turned off when "THC Off" is selected on screen????

I'm just thinking through traps that might stop my revised M03 macro from working and not having permanent access to "ArcOk" would be one of them, this would cause a time-out and stop the job from being able to run.

2303
General Mach Discussion / Re: 1st pierce is longer...
« on: September 10, 2014, 04:06:19 PM »
Ignore my last post, too late to edit it now.

I see block delete is built in function triggered by a line starting with "/"

It was the title "block delete" which made me think it altered the code, however the code my post outputs has line numbers and I have no idea how to get the / code in front of them - from what I've read it must be the first character on a line.

Anyway, my method works ok, at least the option part, as yo the rest of the macro code, time will tell I guess.

2304
General Mach Discussion / Re: Calibrating machine?
« on: September 10, 2014, 01:15:54 PM »
I would try a long steel rule first, over a good distance it's likely more accurate.
Clamp it to the frame with a clear pointer stuck on the moving part and run the axis calibration over the longest distance possible.

2305
General Mach Discussion / Re: 1st pierce is longer...
« 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

2306
General Mach Discussion / Re: 1st pierce is longer...
« 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?

2307
General Mach Discussion / Re: 1st pierce is longer...
« 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.

2308
General Mach Discussion / Re: 1st pierce is longer...
« 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;)

2309
General Mach Discussion / Re: 1st pierce is longer...
« 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?

2310
General Mach Discussion / Re: 1st pierce is longer...
« 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.