Configure PlasmaC with only one BOB

I try this, but then i get the error message,

pin parport.0.pin-11-in-not was already linked to all-home

I think this is because i used one pin for homing and for THC ?

Giuseppe wrote: pin parport.0.pin-11-in-not was already linked to all-home

You can try:
ie, re-use the signal.

Sorry, i can't find information how to re-use the signal.

Giuseppe wrote: Sorry, i can't find information how to re-use the signal.

net all-home => joint.2.home-sw-in ..... from the hal file the bit in blue is the signal

Andy wrote You can try:
net all-home debounce.0.2.in

ie, re-use the signal

.

ie, the signal can be reused for the debounce

OK does i understand it right?

I will change

"net din-001 parport.0.pin-11-in-not => debounce.0.2.in"

from the connections.hal to

"net all-home parport.0.pin-11-in-not => debounce.0.2.in"

and

"net din-001<= debounce.0.2.in"

in the hal file to

"net all-home <= debounce.0.2.in"

ok now the yellow light only turns on when the toarch touchs the bed.
So far so good.

Now i have to fix the EHC enable. This is still on when i start plasmac.

I will try it by my own

So i try this

setp parport.0.pin-16-out-invert 1

but it doesn't work

Giuseppe wrote: OK does i understand it right?

I will change

"net din-001 parport.0.pin-11-in-not => debounce.0.2.in"

from the connections.hal to

"net all-home parport.0.pin-11-in-not => debounce.0.2.in"

and

"net din-001<= debounce.0.2.in"

in the hal file to

"net all-home <= debounce.0.2.in"

A HAL "net" command is

net signal_name hal_pin1 hal_pin2 hal_pin3

With as many hal pins as you want in the net.

The signal name can be anything you want. It should be something that makes sense to you.

The following all do the same thing.

or
Or any variant of that. spread between as many HAL files as you want.

When you tried to re-use parport.0.pin-11-in the system told you that the pin value was already available on the signal "all-home".
A pin can only be connected to one net. But many pins can be connected to the same net.

So if you want to use the value of that pin somewhere else, you re-use the signal name.

Your code above seems to be rather confused.

Back to my cutter.
I think i understand what you are talking about. I hope so

At this moment i think it works not completely right.

When i start plasmac, should the "thc enabled" LED light up? In my case it is so. How can i turn it of for test?
When i use the M64 M65 nothing happens.

Another think thats work is the "Probe test" button. When i click it, the z axis go down until it touches the bed. Then it counts a timer and after this it go back to start position. Is this right function?

Can help someone?

Giuseppe wrote: Back to my cutter.
I think i understand what you are talking about. I hope so

At this moment i think it works not completely right.

When i start plasmac, should the "thc enabled" LED light up? In my case it is so. How can i turn it of for test?
When i use the M64 M65 nothing happens.

Without seeing your gcode it's hard to say. You can disable it manually in the RUN PANEL (or TAB depending how you have it configured). linuxcnc.org/docs/devel/html/plasma/plasmac-user-guide.html#thc

Another think thats work is the "Probe test" button. When i click it, the z axis go down until it touches the bed. Then it counts a timer and after this it go back to start position. Is this right function?

Yes, but there is more to it, after it probes, it is stopping at "pierce height" for the currently selected material. It pauses there so that you can use a gauge block, or feeler gauges, or similar, to measure that the pierce height is accurate. This allows you to compensate for the movement in the float switch. This moment can be compensated for in the config tab under "float travel" in the probing section. linuxcnc.org/docs/devel/html/plasma/plas...e.html#_config_panel

You would keep adjusting this value until the pierce height on the currently displayed material = the pierce height you measure in real life.

linuxcnc.org/docs/devel/html/plasma/plas...de.html#button-probe