It is currently Sat Dec 16, 2017 2:14 am

 

Sheetcam post not right??

Post your questions or tips on SheetCam software in this topic.
davek0974
Posts: 736
Joined: Wed Aug 13, 2014 8:30 am
Location: Hertfordshire, England
Contact:

Sheetcam post not right??

Postby davek0974 » Thu Jun 15, 2017 5:24 am

Ok, so i recently discovered why my THC was not turning off with code snippets - it needed an M22 between S10 calls.

This has created another issue though - the M22 is a delay pause and i now get a pause after starting the cut see code block.
N1590 is the end of the previous segment
N1670 is the start fire of the next segment
So in N1700/10/20 we can see that it fires for the pierce but THEN turns off the THC, surely it should turn off before firing so i don't get the delay???
BTW it turns off twice because the min length for THC is 80mm and I also use a Small-Shapes path rule - maybe i need to get rid of one or the other but i think the M22 will remain.

Any thoughts?

Code: Select all

N1590 M05
N1600 G00 Z20.000
N1610 M09 (Turn off extract fan)
N1620 M01 (Paused: Hit RUN to continue)
N1630 X61.612 Y564.201
N1640 M08 (Turn on extract fan)
N1650 M98 (HeightSense.tap)
N1660 G00 Z2.5000
N1670 M03
o549
N1680 X61.6121 Y564.2006
N1690 G01 Z0.500 F2400.0
N1700 S10 (DTHCa is OFF)
N1710 M22 (On small shapes)
N1720 S10 (THC Off By Code Snippet) (On small shapes)
N1730 X64.612
N1740 Y565.605
N1750 G02 X64.761 Y567.806 I14.201 J0.141
N1760 X66.985 Y570.871 I3.065 J0.115
N1770 G01 X67.064 Y570.883
N1780 X67.086
N1790 X67.105 Y570.8

tcaudle
Posts: 814
Joined: Tue Feb 28, 2012 6:47 pm

Re: Sheetcam post not right??

Postby tcaudle » Thu Jun 15, 2017 11:52 am

The M22 only needs to be there if there are more than one S command with no motion between them. Its because the S command has to be stuffed inot the Speed DRO and MACH has to read it and translate the action in the Plugin. The code needs time to do that and if there is nothing happening it overflows the speed DRO buffer. Using dueling rules is a formula for dysfunction. Its like two people trying to drive the same car at the same time.

The ONLY time you should have two S commands in a row is at the beginning where all of the settings are preloaded at once .

davek0974
Posts: 736
Joined: Wed Aug 13, 2014 8:30 am
Location: Hertfordshire, England
Contact:

Re: Sheetcam post not right??

Postby davek0974 » Thu Jun 15, 2017 1:24 pm

Thanks,

I have been messing with code this afternoon and it seems i can use the sheet cam (min length for THC) setting to control the THC on smaller objects along with a path rule to lower the speed if needed.

This should work as long as the Min-Length setting encompasses the length set in the path rule.

tcaudle
Posts: 814
Joined: Tue Feb 28, 2012 6:47 pm

Re: Sheetcam post not right??

Postby tcaudle » Thu Jun 15, 2017 2:12 pm

Don't complain if it does not work. Mixing cut rules seldom works out well.

davek0974
Posts: 736
Joined: Wed Aug 13, 2014 8:30 am
Location: Hertfordshire, England
Contact:

Re: Sheetcam post not right??

Postby davek0974 » Thu Jun 15, 2017 4:23 pm

Thanks but i can't see how the path rule alone can work - if i leave out the Min-Length option and just use a path rule to slow down and kill the THC, I get his result...

Code: Select all

N0230 G00 Z2.5000
N0240 M03
o549
N0250 X58.7101 Y246.1527
N0260 G01 Z0.500 F2400.0
N0270 S20 (DTHC is ON)
N0280 S10 (THC Off By Code Snippet) (On small shapes)
N0290 G01 X56.153 Y244.585
N0300 G03 X57.506 Y243.891 I1.727 J1.705


So its back to the double S code which fails as before.

If i don't disable the THC when slowing for small shapes and circles, it dives the torch as expected due to running slower, if you don't run slower the cut quality suffers?????


Return to “SheetCam”

Who is online

Users browsing this forum: No registered users and 2 guests