Is someone using Gmoccapy Plasma ?

More
05 Nov 2015 02:00 - 05 Nov 2015 03:46 #64761 by Michael80
yes, i´m right now implementing the THCUD, and the signals looking quite good, but no reaction on Z axis. As i can remember i have connected:

thcud.moveUp <= parport.1.pin-10-in
thcud.moveDown <= parport.1.pin-11-in
thcud.arcok <= parport.1.pin-12-in

thcud.torch-on <= motion.spindle-on
thcud.enabled <= plasma.hal-btn-thc

in halshow it seems working properly,
if i press THC on Gmoccapy thcud.enabled is true
arc-ok is coming,
torch on is ok,
the velocitys are ok
up down is coming

but Z is not moving around

what did i miss?

What PPC do u use in Sheetcam?


EDIT: Meanwhile i updated to 2.7.0 with debian wheezy
Last edit: 05 Nov 2015 03:46 by Michael80.

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

More
05 Nov 2015 05:03 #64773 by mariusl
It is difficult to say why you get no Z movement.
In sheetcam you will find an EMC_plasma post. You might have to edit some items

Regards
Marius


www.bluearccnc.com

The following user(s) said Thank You: Michael80

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

More
05 Nov 2015 05:14 - 05 Nov 2015 06:53 #64774 by Michael80
what about this:

thcud.z-pos-in float in : Z Motor Position Command in from axis.n.motor-pos-cmd
thcud.z-pos-out float out :Z Motor Position Command Out
thcud.z-fb-out float out : Z Position Feedback to Axis
thcud.cur-offset float out : The Current Offset

do i need to do something with this pins?

cause right now i have done nothing with it

BR

Michael

EDIT: Touch Off is working now with the PPC LinuxCNC THC, with little edition, thanks Marius :)
Last edit: 05 Nov 2015 06:53 by Michael80.

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

More
05 Nov 2015 16:52 #64797 by mariusl
I am glad that you are getting it done. I assume that you connected the arc_ok and the up and down signals from the Proma to the parport and then to the THCUD component.
The up/down signals from the Proma will cause the Z axis to move up or down. The THCUD component captures the Z position command and drives the head up and down as required. The movement is not shown on the DRO as it would cause a following error. After the cut is finished, the THCUD component passes the control back to the machine.

Regards
Marius


www.bluearccnc.com

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

More
05 Nov 2015 17:15 #64798 by Michael80
sorry maybe i wrote false .. i only got the Z-Plane Touchoff running, not the THC

do i need to do something with the pins i wrote in the last post?


Maybe, if i get it running, we should update the WIKI that other users can do it easier

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

More
05 Nov 2015 17:52 - 05 Nov 2015 17:54 #64801 by mariusl
Did you read the man pages for the THCUD component?

I will be putting a complete setup on the wiki soon. Busy testing some things at the moment.

Regards
Marius


www.bluearccnc.com

Last edit: 05 Nov 2015 17:54 by mariusl.

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

More
05 Nov 2015 18:33 #64806 by Michael80
yes i read, but found nothing to grap. BUT in some other threads i found some more details. BigJohn wrote an simulation Program to test the THC and now im checking with the commands in there. maybe i can use something.

Z is now passed through and the component shows me the actual Z Value, but still not correcting it. But i think i´m on the right way ;)

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

More
05 Nov 2015 20:12 #64818 by mariusl
Remember that you will not see the correction on the DRO. The Z change is done only in the THCUD component. As far as the controller is concerned the Z never moves during a cut. There is a pin called thcud.cur-offset that when connected to the plasma.hal-lbl-corr it will show you the actual units of correction from the original position. The label is situated in the control panel in the plasma screen.

Regards
Marius


www.bluearccnc.com

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

More
05 Nov 2015 20:38 #64820 by Michael80
so maybe this makes it more clear.

the values are shown in HalShow, not in DRO.
if signal thc-up is coming, the thcud.z-pos-out is changing very fast to a high value > 5000, but Z is not moving.

here are the hal commands i used in customs.hal
loadrt thcud
addf thcud servo-thread

net MoveUp thcud.torch-up <= parport.1.pin-11-in-not
net MoveDown thcud.torch-down <= parport.1.pin-12-in-not
net arc-ok thcud.arc-ok <= motion.digital-in-00 <= parport.1.pin-10-in
net Probe-input motion.probe-input <= parport.0.pin-10-in-not
net thc_torch-on => thcud.torch-on

unlinkp axis.2.motor-pos-cmd
net Zpos thcud.z-pos-in <= axis.2.motor-pos-cmd

unlinkp axis.2.motor-pos-fb
net thc-pos-fb thcud.z-fb-out => stepgen.2.position-cmd axis.2.motor-pos-fb
setp thcud.velocity-tol 4
setp thcud.correction-vel 5

net requested-vel thcud.requested-vel <= motion.requested-vel
net current-vel thcud.current-vel <= motion.current-vel
Attachments:

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

More
05 Nov 2015 20:47 #64821 by mariusl
The correction velocity in you picture shows 50. That might be too much. In plasma mode we do not have the luxury of the trajectory planner to do the acceleration and deceleration for us. So when we do correction it starts off at the acceleration parameter that you set in the THCUD component. If that is too fast the motor will "slip" and you will see no movement on the axis. You must start off very slow and low until you see some movement and then you can start to optimize your system.

But I see no correction in your picture??

"PLASMA SCREWS WITH CNC PRINCIPALS"

Regards
Marius


www.bluearccnc.com

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

Moderators: newbynobiHansU
Time to create page: 0.347 seconds
Powered by Kunena Forum