Advanced Search

I just read the manual on your THC device and it puts out 3 signals arc, up, down. This type of THC connects to the thcud component which accepts an up down input from a THC device. The thcud then hijacks the Z axis with an offset up or down as commanded. After turning off the torch and while moving the Z axis to the safe position any offset is removed.

www.linuxcnc.org/docs/2.7/html/man/man9/thcud.9.html

JT

I think that will not work.
LinuxCNC is a CNC system.
The stepper drive need dir and step informations and no MoveUp (true/false).

If i move the Z-axis direct, i will loose the correct position.
I have to move the head with the Z-value or with an offset value and a reset after the cut is over, or so.

Then you need to use an output pin on the parallel port.

JT

I want that the head moves up if the signal "MoveUp" is true

What do you want to hook the signals to in gmoccopy? Keep in your mind that a parallel port input pin can only be connected to something like a led not to a push button on the screen. This is why I stay confused to what your trying to do.

Can you just say:
I want to push a button on my screen and make the thc go up.
Or
I want the thc to turn on an indicator on my screen when it is moving.

The first on would use and output pin and the second one an input pin.

JT

Hmmm, that is difficult to explain.
LinuxCNC is working in default with the parallel port pins.
The pin 10 is connected with a "MoveUp" signal
The pin 12 is connected with a "MoveDown" signal

So forget the tripleBeast and THC module and so on. It is to easy.
I can see in HalShow both signals MoveUp and MoveDown and that they work on contact.
My question is how to hook up that signals in LinuxCNC (gmoccapy plasma)?

I have no clue what you want to hook the parallel port input pins to? Do you want see a led change state as the input pin is toggled from the beast?

JT

The Beast communicates via parallel port (printer)

The most needed parameters are:

net MoveUp <= parport.0.pin-10-in
net MoveDown <= parport.0.pin-12-in

I can see in HalShow both signals MoveUp and MoveDown and that they work on contact.
But i have no clue how to hook up...

The triple beast appears to be some kind of device that is controlled over the network...

What signals exactly can you see?

JT

What is a "triple beast"?

benezan-electronics.de/shop/product_info...ath=8&products_id=76

At the moment i only want to control the height of the plasma head.
I have a THC controller with two pins with up and down signals.
proma-elektronika.com/index.php/en/produ...trol/compact-thc-150
It is connected with a triple beast.
I can see the signals in the Halshow.
But i have no idea how to connect with gmoccapy (button up/down ?).

ZX-Sinclair wrote:

That's my problem. It is to easy to explain.
At the moment i only want to control the height of the plasma head.
I have a THC controller with two pins with up and down signals.
It is connected with a triple beast.
I can see the signals in the Halshow.
But i have no idea how to connect with gmoccapy (button up/down ?).

What is a "triple beast"?

Can you try and describe what you want to do, I still have no idea what you want.

JT

That's my problem. It is to easy to explain.
At the moment i only want to control the height of the plasma head.
I have a THC controller with two pins with up and down signals.
It is connected with a triple beast.
I can see the signals in the Halshow.
But i have no idea how to connect with gmoccapy (button up/down ?).

Maybe someone else can help, I don't have a clue what you are talking about.

JT

No, i have heared about that. The docu means that is for Mesa cards?
It seems that i have all the needed files...?
I downloaded that:
wiki.linuxcnc.org/cgi-bin/wiki.pl?Gmoccapy_Plasma

Now it works. But like a mill. There is no THC control. I think it is not ready or something is missing.
I took three ref switch pins for Z-up, down and arc ok.
I can see the signals (MoveUp, MoveDown, ArcOk) in the HalShow.
If i try to insert this as a hook in signals.hal or my-machine.hal then the signals panel and/or the plasma panel disappears.
And nothing else happened.

At the moment i would be happy if it stops without ArcOk signal....

If i install thcud i will crush the actual constellation and i have to install the 9th or 10th version...?

This really doesn't have anything to do with Gmoccapy... so far.

Did you load the thcud component in your hal file?

JT