Manual tool change + tool lengh touch off

debounce needs to be added to the hal file. The process is much the same for any HAL component.

1) load the component: This loads a 1 channel debounce called debounce.0

2) Make the debounce function run in the base thread:
3) set the debounce time:
4) put the debounce between the parport and the probe input

I had to change the last comands to:

setp debounce.0.delay 10
net probe-raw parport.0.pin-10-in-not => debounce.0.0.in
net probe-in <= debounce.0.0.out

otherwise I got errors. I hope the function is the same?

axel88 wrote:

which hal file?
/usr/share/emc/tcl/bin/halconfig.tcl?

EDIT: /home/axel/emc2/configs/Portalfrase/Portalfrase.hal looks good, right?

Yes, I came into the forum at a run to make sure you weren't about to do something silly.

(I had to delete your umlauts as the forum refuses to show any message with odd characters at all, including three full stops in a row, and the UK currency symbol)

You can either edit that file, or if it was created by stepconf you can put your new stuff in the custom.hal file where stepconf won't over-write it.

The drawback with putting it in the custom.hal file is that you might need to unlink some connections to insert your new stuff. Would do that.

HAL is one of the most powerful features of EMC2, it allows you to connect any inputs and any outputs together in a completely free way, optionally processing the signals on the way.

1.) By moving the debounce procedure to the custom.hal I've got some errors:

CUSTOM.HAL (line 4 to 10) ERROR:

2.) I've got problems with the subprograms:

I wrote to files: first-tool.ngc and auto-tool-change.ngc and located them in ../emc/nc-files which is defined as the PROGRAM_PREFIX folder in the Portalfrase.ini .

when I run: or the error "File not open" appears.

here is my subprogramm:
But even if I copy the fred.ngc example it doesn't work.

axel88 wrote:

custom.hal:10: Signal name 'debounce:0.0.out must not be the same as pin.

Sorry, I didn't put the signal name in the net statement, so the interpreter is trying to use the first pin name as a signal name

You need something like

net FreelyChosenSignalName debounce.0.0.out => motion.probe-input

The signal names are conceptually equivalent to the colours of the wires in a physical system, you can choose any you want, but it helps understand the system if they match the function. (Also you can't have more than one signal with the same signal name)