connection -> gmoccapy to THC

More
18 Aug 2015 09:40 - 18 Aug 2015 16:43 #61502 by ZX-Sinclair
I know the link to the manpage.
It's only a short description.
Are there any further informations?

If i insert in the .hal
loadrt thcud
and
thc.torch-up <= paraport.0.pin-15-in

Error message: thc.torch-up
Update:
This sentence:
thc.torch-up <= paraport.0.pin-12-in thc.torch-down <= paraport.0.pin-13-in motion.spindle-on => parport.0.pin-16-out (start the arc) thc.arc-ok <= motion.digital-in-00 <= parport.0.pin-15-in
from manpage means:
net thc.torch-up <= parport.0.pin-15-in
net thc.torch-down <= parport.0.pin-10-in
net thc.requested-vel <= motion.requested-vel
net thc.current-vel <= motion.current-vel

Next error: the name is parport, NOT paraport

And so on. At the moment it works, but always without Up/Down
Last edit: 18 Aug 2015 16:43 by ZX-Sinclair.

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

More
18 Aug 2015 16:49 - 18 Aug 2015 16:58 #61503 by cncbasher

I know the link to the manpage.
It's only a short description.
Are there any further informations?

If i insert in the .hal
loadrt thcud
and
thc.torch-up <= paraport.0.pin-15-in

Error message: thc.torch-up
Update:
This sentence:
thc.torch-up <= paraport.0.pin-12-in thc.torch-down <= paraport.0.pin-13-in motion.spindle-on => parport.0.pin-16-out (start the arc) thc.arc-ok <= motion.digital-in-00 <= parport.0.pin-15-in
from manpage means:
net thc.torch-up <= parport.0.pin-15-in
net thc.torch-down <= parport.0.pin-10-in
net thc.requested-vel <= motion.requested-vel
net thc.current-vel <= motion.current-vel

Next error: the name is parport, NOT paraport

And so on. At the moment it works, but always without Up/Down


typo should be
parport.0.pin-12-in thc.torch-down <= parport.0.pin-13-in
Last edit: 18 Aug 2015 16:58 by cncbasher.

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

More
18 Aug 2015 18:55 #61504 by BigJohnT

I know the link to the manpage.
It's only a short description.
Are there any further informations?

If i insert in the .hal
loadrt thcud
and
thc.torch-up <= paraport.0.pin-15-in

Error message: thc.torch-up


The man page is all the documentation for the thcud component and is quite elaborate compared to most man pages.

Lets start at the top:
First you have to load the component in your hal file with:
loadrt thcud

Next in Axis (I don't know about other GUI's) run Show Hal Configuration and see what the name of the thcud function is. Then you have to 'add' the thcud component to a thread so it will actual do something with:
addf thcud base-thread

Next looking in Show Hal Configuration Pins find the exact name of the pins you wish to connect to and using the net command and a signal name connect them.
net torch-up thcud.torch-up <= paraport.0.pin-12-in

Please read about the net command here:

www.linuxcnc.org/docs/2.7/html/hal/basic-hal.html

JT

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

More
18 Aug 2015 19:37 - 18 Aug 2015 19:38 #61505 by ZX-Sinclair
Ah, ok! :-)

I have the same HalShow than in axis.
If i select "functions", there is a lot of stuff and "thcud".
And selected:
owner 12
CodeAddr f8ff0000
Argf8ff8
FP yes
users 0
name thcud


after i inserted in my hal:
addf thcud base-thread
i get the error message:
error ; function  'thcud' needs FP

What does that mean? FP is YES
Last edit: 18 Aug 2015 19:38 by ZX-Sinclair.

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

More
18 Aug 2015 20:38 #61508 by Todd Zuercher
It means that it needs to be in a floating point thread (such as the servo-thread), and the base-thread you have it in is non-floating point. it is possible to configure the base thread to support a floating point.

see: linuxcnc.org/docs/html/man/man9/motion.9.html

You will need to find base_thread_fp=0 and change it to base_thread_fp=1 (or add it if it does not exist.)

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

More
19 Aug 2015 01:42 #61524 by ZX-Sinclair
I think i'm to stupid for that.
Since two weeks the machine is ready and has to run.
It is cheaper if a specialist flies from USA and adjusts the parameters.
And i understand nothing.

I have searched in all files.
"base_thread_fp=0" doesn't exist

So i have added this
"base_thread_fp=1" in the .hal
- error: unknown command

with the addf in front:
- error: addf needs 2 args

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

More
19 Aug 2015 01:46 #61525 by BigJohnT
Just leave the base-thread alone and add the function to the servo-thread.

JT

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

More
19 Aug 2015 02:09 #61526 by ZX-Sinclair
I'm confused...

what means:
"leave the base-thread alone"?

addf thcud base-thread (=error)
thcud base-thread (=error unknown command)
base-thread (=error unknown command)

and which part is the servo thread?
iIn my HAL are things like:
"addf stepgen.capture-position servo-thread"
Is that the servo-thread?
Should i insert "addf thcud base-thread" behind that part or "base_thread_fp=1 "

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

More
19 Aug 2015 02:19 #61528 by BigJohnT
That means don't change the base thread to floating point as Todd suggested. You can't just guess what to put in the hal file it only supports a few commands like net, addf, sets, setp and they have specific format.

If the thcud component uses FP (Floating Point) then add it to the servo thread just like other functions have been added to the servo thread. It's my fault I assumed the thcud was not using FP so I told you wrong.
loadrt thcud
addf thcud servo-thread

This should get the component up and running then you have to use the net command to connect the pins.

JT

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

More
19 Aug 2015 17:26 #61545 by ZX-Sinclair
Ok,

i inserted "addf thcud servo-thread" in my HAL
No error during start up, but my signals and plasma panel is away! :-(
I know that effect.
This is my "Signals.HAL":
# Hook up signal pins connecting

# Out pin
#net MoveDown      => signals.led_MoveDown
#net MoveUp        => signals.led_MoveUp
#net FloatSwitch   => signals.led_FloatSwitch
#net ArcOK         => signals.led_ArcOK
#net TorchOn       => signals.led_TorchOn
#net HeightLock    => signals.led_HeightLock
If i remove one # i have the same effect.

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

Time to create page: 0.276 seconds
Powered by Kunena Forum