Manual tool change + tool lengh touch off

More
15 years 11 months ago #5682 by andypugh
The problem might be the hyphen in the name. (Just a guess). Try it without that. The way that filenames get passed through the G-Code interpreter is a bit messy, they get changed to all lower-case and spaces get removed, the same might be true for "operators".

Please Log in or Create an account to join the conversation.

More
15 years 11 months ago #5683 by axel88
Code:
unlinkp parport.0.pin-10-in-not unlinkp motion.probe-input loadrt debounce cfg=1 addf debounce.0 base-thread setp debounce.0.delay 10 net probe-raw parport.0.pin-10-in-not => debounce.0.0.in net motion.probe.input <= debounce.0.0.out

I thought I tried this at first, but so it worked.

The hyphen is not the reason, I've already tried it without and the fred.ngc has none either.

Please Log in or Create an account to join the conversation.

More
15 years 11 months ago #5686 by axel88
It seems to work if i call o<first-tool> call in a *.ngc file, but I can't run it from the MDI console. But this should be enough for the postprocessor.

Please Log in or Create an account to join the conversation.

More
15 years 11 months ago #5687 by andypugh
Which EMC2 version are you running?

I vaguely recall an improvement in the way it searched for subroutines, but that was rather a long time ago.

I just did a test:

In the ini file I have PROGRAM_PREFIX = /home/andypugh/emc/nc_files

In the nc_files directory I have:
test1.ngc
test.ngc

test1.ngc contains:
Code:
o<test> call m2
test.ngc contains:
Code:
o<test> sub (debug, We got here) o<test> endsub m2
And it all "just works" with version 2.3.5

Incidentally, the dev list was busy last night sorting out an issue with probing in subroutines. I think it is only a problem when the subroutine is called from MDI_COMMAND, but I have asked for clarification. The issue is one of returning before the end of the probe, I think, so not related to your general subroutine problem.

Please Log in or Create an account to join the conversation.

More
15 years 11 months ago - 15 years 11 months ago #5688 by BigJohnT
You could use something similar to my touchoff file that I use on my plasma torch.

move to start point of the cut...
o<touchoff> call [0.080] [0.02] [0.06] (Touchoff and start torch)
...


my touchoff.ngc file:

o<touchoff> sub
(#1 pierce height, #2 pierce delay, #3 cut height)
F10
G38.2 Z-1.75 (Probe to find the surface)
G91
G1 Z0.070 (Raise up to Z0)
G90
G92 Z0 (Set Z0)
G1 Z#1
M3 S1
M66 P0 L1 Q5 (Wait for Arc OK from Torch)
G4 P#2 (Pause for pierce delay)
F25
Z#3 (goto cut height)
o<touchoff> endsub
M2

John
Last edit: 15 years 11 months ago by BigJohnT.

Please Log in or Create an account to join the conversation.

More
15 years 11 months ago #5690 by andypugh
axel88 wrote:

It seems to work if i call o<first-tool> call in a *.ngc file, but I can't run it from the MDI console. But this should be enough for the postprocessor.


Ah, yes. I didn't realise that you were calling it from MDI. I just tried it in version 2.4.3 and it worked fine. Perhaps you are using 2.3?

Please Log in or Create an account to join the conversation.

Time to create page: 0.465 seconds
Powered by Kunena Forum